Capture a ticket

Capture a ticket

Turn a rough idea (or a thoughts/ document) into a well-formed ticket on the active tracker. Input: $ARGUMENTS

First read ${CLAUDE_PLUGIN_ROOT}/references/trackers.md and determine the active tracker (GitHub Issues or Linear) and its create/status operations.

• GitHub needs the gh CLI authenticated (gh auth status).
• Linear needs the mcp__linear__* tools (authenticate via /mcp).

If the chosen tracker isn't available, say so and stop.

The hard rule

Every ticket MUST contain a "Problem to solve" stated from the user's perspective. If the user gives only implementation details, you MUST ask:

"To write a good ticket, please explain the problem you're trying to solve from a user's perspective."

Do not create a ticket without it.

Steps

1. If given a thoughts/ path, read it fully. Distil the core problem and any decisions.
2. Draft the ticket and show it to the user for confirmation:
   • Title — clear, action-oriented
   • Problem to solve — 2-3 sentences, user-facing
   • Solution outline — only if well-defined
   • References — link source docs and path/to/file.ext:line code refs
3. Create it via the active tracker's "Create a ticket" operation, starting in the triage status (GitHub: tf:triage label; Linear: Triage state).
4. Return the ticket URL / number.

Keep tickets scannable. Focus on "what" and "why"; include "how" only when concrete.