Auto mode

Ship a ticket end to end.

Not every ticket needs the same level of hand-holding. Some are creative problems you want to think through. Others are obvious scaffolding you just want done. Storybloq gives you three gears: collaborate, targeted auto, or full-backlog auto. Same state machine underneath, different amount of you in the loop.

Coming soon

Follow along

  1. 1.

    Collaborate: think it through, then execute

    For work that needs your input, ask Claude Code to pull a ticket off the top of the backlog. Discuss it. Plan it together. When you're happy with the plan, tell Claude to execute. The state machine takes over: writes tests, implements, reviews, finalises. You owned the thinking, Claude owned the typing.

  2. 2.

    Targeted auto: /story auto T-001

    When a ticket is obvious scaffolding (set up Next.js, wire up Tailwind, add a route), skip the conversation. Run /story auto with the ticket ID. Plan, Codex review, your approval, then tests, implementation, review, finalise. No typing from you after the plan is approved.

    $/story auto T-001
  3. 3.

    Full-backlog auto: /story auto

    Got a whole phase of scaffolding to burn through? Run /story auto with no ticket ID. The machine picks the next unblocked ticket, ships it, picks the next, and keeps going until the backlog drains or it hits something that needs you. Capped by maxTicketsPerSession in .story/config.json.

    $/story auto
  4. 4.

    Approve the plan (every mode)

    The first real pause is always PLAN_REVIEW. Claude's plan, Codex's findings, the refined plan. You approve, tweak, or reject. This is where you catch wrong assumptions cheaply, before any code is written.

  5. 5.

    Watch it run

    After approval 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. Typical round trip: tens of minutes per ticket.

  6. 6.

    Review the handover and commit

    On COMPLETE the machine writes a handover: what it shipped, what it skipped, any followup issues it logged. Read it, review the diff, commit. Ticket done. If you ran full-backlog auto, it moves to the next one and does it again.