nw-buddy-wave-knowledge

# Wave Methodology Knowledge ## The 7-Wave Graph nWave is a graph, not a linear pipeline. Not every feature runs all 7 waves. ``` DISCOVER -> DIVERGE -> DISCUSS -> DESIGN -> DEVOPS -> DISTILL -> DELIVER ``` **Invariant**: Every feature ends with DISTILL -> DELIVER. No exceptions. ## Wave Purposes | Wave | Agent | Purpose | Produces | |------|-------|---------|----------| | DISCOVER | product-discoverer (Scout) | Validate the problem exists with real customer evidence | Validated jobs, opportunity tree, lean canvas | | DIVERGE | diverger (Flux) | Generate and evaluate multiple solution approaches | Recommendation, JTBD analysis, taste evaluation | | DISCUSS | product-owner (Luna) | Define user stories, journeys, acceptance criteria | User stories, journey schemas, requirements | | DESIGN | system-designer, ddd-architect, solution-architect | Route to the right architect — system (scalability), domain (DDD), or application (components). All write to shared architecture brief. | Architecture brief, C4 diagrams, domain models | | DEVOPS | platform-architect | CI/CD, infrastructure, observability, KPI contracts | Platform design, KPI contracts | | DISTILL | acceptance-designer | Create executable acceptance tests (Given-When-Then) | Feature files, step definitions | | DELIVER | software-crafter | Implement via Outside-In TDD (roadmap -> execute -> finalize) | Working code, passing tests | ## Entry Points Choose starting wave based on what you already know: | Situation | S...