v0.1 to v0.2

---

name: attach-to-ticket

description: Attach pasted images, files or URLs to a fetched ticket, saved beside its ticket file and referenced from it, or fill an attachment the fetch could not download. Local only — never queries or edits the tracker.

license: MIT

metadata:

---

# Attach to ticket

Save assets — pasted images, local files, URLs — into a ticket's planning directory and reference

them from its ticket file, so a fresh session picks them up. **Local only** — never query or modify

the tracker (no API calls, no re-fetch, no comments or edits); downloading an asset URL the user

supplies or a not-downloaded entry names is fine, tracker-hosted or not. Edit nothing in the

documents beyond the entries below and the REQUIREMENTS line of step 6.

## Your task

1. **Collect the assets.** The images pasted with the invocation, plus paths and URLs in its text;

images pasted earlier only when the user points at them. Nothing pasted or pointed at → ask

which, listing the images seen in the session. Done when every supplied asset is collected or

dropped by the user.

2. **Resolve the ticket.** Named in the argument or already in the session (fetched, read,

discussed) → proceed. Otherwise guess (branch name, latest planning directory) and confirm

3. **Pick the document** — unless the user names one: the ticket file, latest `-vN` (file or

directory) when re-fetched, the `<id>-` one in a shared directory; the REQUIREMENTS file when no

ticket file exists. Several candidates left → ask.

4. **Map assets to entries.** Descriptions map to assets in paste order; "image 2 is …" overrides.

If the document has entries whose file is missing (attachments or design references, marked

not downloaded or not), propose which asset fills which — by original filename or design name

and what the image shows — and confirm, unless the user's text already says. An asset with no

description → ask what it shows, recommending a caption read off the image; never write one

silently.

5. **Save to disk** — see Sources; never route bytes through the model (output caps truncate base64

6. **Write the entries.** Filling an entry: keep it, drop any not-downloaded note, add or rewrite

its reference to match the saved file (image → embed, else link; its extension), add the

Else append to `## Attachments` (create it when missing — last, or before

`## Design references`):

```markdown

### Attachment 3


_<description> — added by hand YYYY-MM-DD_

```

Non-image → `[attachment-3.pdf](attachment-3.pdf) — _<description> — added by hand YYYY-MM-DD_`.

`attachment-3` stands for the saved filename, `<id>-` prefix included. When the document is a

ticket file and a REQUIREMENTS file exists for it (its base with `.TICKET` → `.REQUIREMENTS`;

for a `-vN` re-fetch with none, the ticket's latest), also append one line per asset — the same

embed or link, its path relative to the REQUIREMENTS file when that sits in another directory,

plus the caption — at the end of its **Context** part; no new section, nothing else changed.

7. **Report** project-relative paths: the document, the REQUIREMENTS file when it got a line — its

`claude --name refine-<slug> "/refine-ticket <document>"`), then the alternative, the tool's

clear command (e.g. `/clear`) followed by `/refine-ticket <document>`.

## Sources

Escape paths and URLs from user or ticket text in every command for the shell running it (POSIX

`'` → `'\''`, PowerShell `'` → `''`), and again for a nested language (AppleScript, PowerShell).

- **Local path** — copy the file.

- **URL** — HTTP(S) only, redirects included (`curl.exe` on Windows):

`curl -fSL --proto '=http,https' --proto-redir '=http,https' -o '<file>' -- '<url>'`; no auth

flows here — on failure or a login page, ask the user to download the file and paste its path.