Ticket Analysis

Slash trigger: /ticket

Analyze a ticket (Jira, Linear, GitHub issue, or pasted description) for requirements, impact, and implementation plan. Do NOT write code.

Hard rules

• MUST read onboarding state files before exploring source code.
• MUST NOT write or modify code — analysis and planning only.
• NEVER scan the entire codebase — inspect only repos/modules/files relevant to the ticket.
• If docs/onboarding/ is missing, tell the user to run /start first.

Required reads (in order)

All paths under docs/onboarding/ (or configured docs_path):