wf-planner

A design-first plan identifies the user problem and scope, then outlines system components, boundaries, and interfaces. It helps avoid scope creep and miscommunication by producing clear execution plans with diagrams, data flows, and milestone sequencing.

Breaking complex architecture changes into testable milestones involves risk ordering and sequencing work into observable chunks. This approach aligns with living documentation like ARCHITECTURE.md to ensure each milestone remains executable and testable.

Yes, you can use this planner to define system boundaries and data flows for feature design. It generates a design-first plan that explicitly outlines system components, interactions, and interfaces to satisfy feature design requirements.

Documentation sync aligns generated design plans with ARCHITECTURE.md and PRINCIPLES.md to seed living docs. During a feature kickoff, it ensures the outlined system components and milestone roadmaps remain continuously synchronized with existing architectural documentation.

You need to generate system design diagrams and milestone roadmaps when starting a feature, applying them to architecture changes or complex work. This design-first planning prevents scope creep by producing clear, actionable execution plans before coding begins.