address-ticket

Read the JIRA ticket for the current branch and drive it to completion using a multi-agent team with TDD: a PO writes requirements, the developer approves, then a test plan is proposed and reviewed. Once confirmed, tests are written first (red), then production code is implemented to make them pass (green).

Usage:

• /address-ticket - Retrieve the ticket and drive it to full implementation with a team
• /address-ticket --no-jira <instructions> - Skip JIRA retrieval and use the provided instructions as the ticket context
• /address-ticket --headless - Fully autonomous: a reviewer agent validates the requirements and test plan instead of asking the developer
• /address-ticket --no-jira --headless <instructions> - Both flags can be combined

Instructions:

Phase 0 — Parse flags

0. Scan $1, $2, $3 for flags:

   Two optional flags can appear in any order: --no-jira and --headless. Any remaining (non-flag) argument is the user instructions.

   • --headless mode: If any of $1, $2, $3 is --headless, set headless = true. In headless mode, the developer is never asked for approval. Instead, a reviewer sub-agent validates the requirements and test plan autonomously (see steps 10 and 14).
   • --no-jira mode: If any of $1, $2, $3 is --no-jira:
     • The first non-flag argument is the user instructions — the ticket context (what to build, fix, or change)