Best For
Best for teams adopting a repeatable delivery rhythm with clear checkpoints.
- Use PRD -> stories -> implementation sequence
- Gate each phase with explicit validation
- Integrate release prep into normal workflow
Documentation
FLOW • v2.0.78Workflow Guide
Canonical runbook for PRD-first execution from planning through release and stabilization.
FLOW Context Profile53Core agents
61Claude skills
64Copilot agents
60Cursor rules
60Codex skills
61Gemini skills
Anti-Patterns To Avoid
These behaviors reduce framework signal and increase rework risk.
- Large changes without story decomposition
- Validation postponed to end
- No release readiness criteria
Adoption Plan
- Draft PRD with measurable acceptance
- Generate stories and assign execution
- Run go/forge with validation
- Ship with release checklist
/prd "feature"
/stories
/go
/ship
Primary References
Operational Checklist
- Version alignment confirmed (v2.0.78)
- Execution evidence captured in stories or PR
- Gate validations completed before merge/deploy