Workflows and stage contractsThe seven stages are a default, not a law. Stages, their contracts and their transitions are data, so an alternative SDLC ships as a document rather than a fork.Stage contractsA contract is the list of sections a card must carry to leave a stage, plus optional checks. You can add sections, rename them, or require your own (a threat model before Deliver, a rollback note before Close) per project in Settings, or ship them in a plugin.One rule is not negotiable: a stage cannot remove its decision gate. A workflow that leaves no way back is rejected by grid workflow check.Workflow documentsMarkdown with a front-matter stage list and one block per transition, stored in <config>/workflows/ and selected per project.---name: trunk-onlystages: [Inbox, Prepare, Doing, Review]---## Prepare -> Doingtrigger: plan-approvedcommand: claude /build {card.md} --plan {plan.md}## Doing -> Reviewtrigger: agent-donecommand: claude /self-review {diff}
EXAMPLESHAPEtrunk-onlyFour stages, no Deliver: for repositories that commit straight to main.regulatedTwo review gates, one technical and one sign-off, with a required approver.solo-fastPrepare, Doing, Review. Delivery is manual and deliberate.