Recommended workflow
product-development-workflow
Build a product from zero
Start here
Begin with discovery and requirements. Before code, map the accepted repository stack and conventions, then load only the capabilities required by the active phase.
Workflow details4 fields
- Use when
- A product opportunity needs to move from discovery and requirements toward release and learning.
- Boundary
- Owns the end-to-end product lifecycle; it does not replace the specialist capabilities selected inside each phase.
- Evidence
- Accepted problem framing, requirements, repository constraints, implementation evidence, release verification, and learning outcomes.
- Completion gate
- The product increment is released or explicitly stopped, verified against its accepted requirements, and handed into a documented learning loop.