Cards, capture and the seven stagesA card is a markdown file with a contract: the sections it must carry depend on which stage it is in. Stages move on triggers, and each transition runs a command you can see and change.Capture: how a card gets inCapture is deliberately dumb. A title and a sentence are enough; Prepare does the work of turning that into something buildable.FROMHOWIn the app⌘N anywhere, or the ＋ Add button on the Inbox and Prepare columns.PhoneThe ＋ tab, typed or held to talk. The project is read from your words.Command linegrid card new "partner keys have no rate limit"From the code viewSelect lines, right-click, "Capture a card here". The file and line range travel with the card.From an errorThe bug report panel offers "file this as a card", with the obfuscated payload attached.ScheduledRecurring cards, for example dependency bumps or coverage sweeps, file themselves on a schedule you set.
At capture you can also set the model, the effort level and the autonomy for this card. Leave them on Default and Grid Console advises from the description: a one-line copy fix does not need the expensive model, a migration does.The seven stagesEvery stage has a scope and a contract. The contract is the list of sections the card must carry before it can leave that stage, and it is configurable per project in Settings.STAGESCOPE AND REQUIRED SECTIONSInboxCaptured, not started. Nothing runs. No contract: it is a queue.PrepareRefines the card until it is pickable. Required: Summary; What I will change; How I will know it works; Requires your attention; Expected files I will touch; List of tasks; Asked questions with your answers. Prepare also decides whether the work can be isolated in a worktree and tested there.DoingBuilds. The card is the live progress report. Required: Summary; Changes so far; Changes still to do; Task list with ticks; Requires your attention.ReviewEverything Prepare promised and Doing did, side by side. Required: all Prepare and Doing sections, plus what is done, what changed from the plan, and the local run with its port.DeliverCreates the delivery as configured (pull request, merge request or push) and reports back with the link. It also monitors the deployment that follows.VerifyChecks the delivery landed and nothing around it broke: merged, deploy green, regression sweep over the rest of the project.CloseWraps up: memory written, documentation updated, one final conflict check across the project.
Transitions are hook pointsEach arrow between stages has a trigger and a command. The commands below are contributed by the bundled Claude provider plugin, not by the core: swap the provider and they change with it.TRANSITIONTRIGGER AND COMMANDInbox → PrepareWhen you file it. claude /prepare {card.md}Prepare → DoingOn your plan approve. claude /build {card.md} --plan {plan.md}Doing → ReviewAgent declares done. claude /self-review {diff}Review → DeliverOn your review approve. git commit && gh pr create --fillDeliver → VerifyAutomatic. make testVerify → CloseOn green. grid memory write {outcome}
A plugin can take over any arrow: gate it, reroute it, or run something first. See Plugins for the stage.transition hook, and Workflows for shipping an entirely different pipeline.Decisions and the way backEvery gate has a reverse. Approving is never the only option: Revise sends the card back with your note, Reject to Inbox parks it, and Reject and close undoes the changes. Review can be done per change, approving or reverting file by file, or all at once.