The Flow field guide
Build with
intention.
Start from what you are trying to do. Each entry leads to the page that owns it, and every page is also available as Markdown.
Start
Install Flow, understand what it is, and pick a foundation.
Workflows
Move a change from intent to verified, live software.
Engineering practices
Practices that keep agent work bounded, safe, and evidenced.
- Manage scope and costHow Flow uses an appetite and a scope guard to keep agent work inside what an increment is worth, and why that is a trade-off practice rather than a spending limit.
- Direct agents safelyWhere Flow's guidance helps an agent act within your authority, where real enforcement comes from instead, and which changes still wait for a person.
- Understand delivery evidenceHow Flow carries a change from stated intent to a reviewed, checked, landed commit, and what each kind of evidence along the way does and does not prove.
- Maintain contextKeep PRODUCT.md, DESIGN.md, and the glossary aligned.
- Model the domainSettle what the project's terms mean.
- PrinciplesOptional themes: validation, observability, agentic, lean, velocity.
- All capabilitiesEvery published capability, by group.
- ArticlesLonger explanations with real examples.
Reference
Look up a skill, a term, or the rationale behind a rule.
Agents
What agent hosts need and how agents read this site.
Want the reasoning behind a practice? Browse capabilities or read the articles.
Recent decisions
All decisions- 0070A research skill, clearer names, and an outcome in every initiative specAccepted
- 0069Direction changes gate at adoption, not discussionAccepted
- 0068The experience skill and the new-skill testAccepted
- 0067Flow boundaries: plugin, starters, scripts, hostAccepted
- 0066Specs sized by delivery, not lengthAccepted