To Tickets

Break a plan, spec, or conversation into a set of tickets — tracer-bullet vertical slices, each declaring the tickets that block it.

Tracker

Default: local markdown in the project's docs/ directory. Unless the user explicitly says otherwise, publish tickets as one markdown file per ticket under docs/<feature-slug>/issues/<NN>-<slug>.md (numbered from 01) — do not touch any external tracker. Record triage state as a Status: line in each file.

Overrides — only when the user explicitly names one in this request:

• jira → create one issue per ticket in Jira via the Atlassian MCP (ask before writing; use the repo's default project), wiring native blocking / sub-task links, applying the ready-for-agent label.
• gh → create one issue per ticket via the gh CLI in the repo's GitHub Issues, wiring native sub-issue / blocking links, applying the ready-for-agent label.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.

2. Explore the codebase (optional)