feature-planning

Feature planning transforms feature requests into sequenced implementation plans by clarifying scope, identifying codebase touchpoints, and breaking work into milestones with acceptance criteria and validation checkpoints. It ensures engineers can start working immediately without re-discovering the codebase.

Defining acceptance criteria involves confirming goals, constraints, and non-goals, then inspecting current code paths to produce small, verifiable tasks. This approach ensures each milestone in the implementation plan has concrete validation checkpoints tailored to existing repository patterns.

Yes, feature planning conducts repository-informed analysis to identify likely code changes by inspecting current code paths, types, tests, and similar features. It provides concrete file and path references alongside repo-specific commands, eliminating the need for manual codebase discovery.

Feature planning applies to any software engineering task where scope must be clarified, regardless of the specific framework. It relies on analyzing existing repository patterns, types, and tests to generate an implementation plan with concrete file references rather than framework-specific assumptions.

Feature planning explicitly surfaces risks, dependencies, and unanswered questions as part of the generated implementation plan. Addressing these constraints early ensures the sequenced tasks and validation checkpoints account for potential unknowns before engineering delivery begins.