Development Workflow
Two dead workflows, one command, and the rules that survived.
Start here
Our AI Dev Workflow Died Twice. Here's the Autopsy.
Roles killed the first generation. Process killed the second. What survived is one slash command.
Branches
Branch AMechanism
How one command runs three stacks without asking
- 1Every Phase Gate in /develop Wants an Artifact, Not a Sentence
How evidence and human decisions move a development run forward.
- 2A Role File Is a Class. A Project's Rule File Is an Instance.
Where knowledge lives when three stacks share one command, layer by layer from longest-lived to disposable.
Branch BLifecycle
Which rules die, and what decides
- 1Every Dead Rule Has a Cause of Death. Living Ones Only Prove They Haven't Died Yet.
Four ways a rule file dies, the retro that decides, and the two ways the retro fooled itself.