To Tickets Agentic

Break a plan, spec, or conversation into tracer-bullet vertical slices. Every ticket declares its blockers, implementation lane, and test seams.

The issue tracker and triage-label vocabulary should be configured. Run /setup-agent-skills if they are missing.

1. Gather context

Use the current conversation. When the user supplies a spec, issue, or URL, read its full body and comments. Read relevant domain docs and ADRs.

2. Explore when needed

Explore enough code to understand existing seams, likely overlap, and prefactoring opportunities. Prefer making the change easy before making the easy change.

3. Draft vertical slices

Each ticket must: