What problem does it solve? It prevents teams from skipping critical planning and verification steps when building software, enforcing evidence-based gates at every stage from idea to deployment so nothing ships on vibes or unchecked boxes. ## Core Features & Use Cases - Gated stage progression: Walks a project through 11 stages (idea, research, scope, PRD, ADR, contract, cards) where each gate must pass deterministic checks before the next unlocks. - Two operating modes: Teach mode makes learners write every artifact themselves; work mode interviews the operator once, drafts the stages, and pauses only at scope sign-off. - Autonomous build driver: The /flow auto command runs a preflight check, then dispatches one subagent per card with dependency-aware parallel grouping, world-state evidence requirements, and a resumable AUTO-LOG.md. - Use Case: A solo founder with a SaaS idea runs /flow next to unlock stage 00, fills the idea template, and the gatekeeper refuses to advance until the research stage contains real evidence with named first-10-users channels. ## Quick Start Ask the assistant to run /flow status to see where your project stands and what is blocking the next gate.
