feature

A structured feature development workflow enforces a five-phase process spanning discuss, BOM, architect, test plan, and implement. It aligns cross-functional teams through mandatory questions and auto-generates consistent documentation artifacts for full traceability.

To start managing a new feature, provide a feature name and scope to initiate Phase 1. The workflow then guides you through requirements gathering, architecture, test planning, and implementation while automatically generating tracking files like description.md and todos.md.

Yes, the feature management workflow supports resumption and auditing across its five phases. If interrupted, you can pick up the process directly, using the auto-generated journey.md and scratchpad.md files to track progress and review previous decisions.

Yes, the workflow auto-generates documentation scaffolding including description.md, todos.md, journey.md, test-plan.md, and scratchpad.md. These files capture cross-functional decisions and track progress to ensure role-agnostic alignment among product, design, and engineering teams.

You need a multi-phase workflow when initiating new features or major changes that require strict alignment across product, design, and engineering. It prevents chaotic execution by enforcing mandatory questions and structured planning from discussion through final implementation.