Auto mode

Ship a ticket end to end.

Once a ticket is well-scoped, you shouldn't have to hand-hold every step. /story auto hands the ticket to a state machine that plans, gets a second opinion, writes tests, implements, tests, reviews, and finalises. You watch and approve the few moments that need your judgement.

Coming soon

Follow along

  1. 1.

    Pick a ticket

    Any unblocked ticket with clear acceptance criteria is a good candidate. For storybook, let's run auto on T-001: scaffold the Next.js project. Confirm it's unblocked by looking at its blockedBy field, then you're ready.

  2. 2.

    Run /story auto

    Inside Claude Code, type /story auto followed by the ticket ID. Press Return. The state machine spins up.

    $/story auto T-001
  3. 3.

    Approve the plan

    The first real stop is PLAN_REVIEW. Claude has drafted an implementation plan and Codex has reviewed it. You see both: Claude's plan, Codex's findings, and the refined plan. Approve, tweak, or reject.

  4. 4.

    Let it run

    After PLAN approved, the machine writes tests, implements to pass them, runs them, runs code review (Claude + Codex + lenses), and finalises. Heartbeats tick in the Mac app so you always know where it is. Average round trip: tens of minutes.

  5. 5.

    Review the handover and commit

    On COMPLETE, the machine writes a handover summarising what it shipped, what it skipped, and any followup issues it logged. You read it, review the final diff, and merge. Ticket done.