ticket-attach-docs

Run the command at the end of the work session; it collects files from the plans directory, matches them to the ticket, and uploads them through a subagent. It proposes create, update, or skip per file and asks for confirmation before uploading.

The briefing and the implementation plan are always attached. Other files are judged by whether they carry unique content someone would have to redo; files duplicating ticket content, superseded drafts, secrets, or restricted internal dumps are skipped.

Yes, the tracker is resolved at run time via the workflow-identify skill, and the appropriate tracker skill is loaded before any commands run. It never assumes a tracker supports documents and adapts to attachments or comments instead.

Repeat runs are expected. Document carriers are matched by title and updated in place, while attachment and comment carriers are compared by content and re-uploaded only when changed; unchanged content is skipped.

No. It never changes ticket state, assignee, labels, or priority, and it uploads files exactly as written without rewriting or reformatting. Files containing secrets are skipped rather than silently edited.