goddard-app-feature-planner

Feature planning prevents drift from current architecture by enforcing alignment with spec, glossary, and planning docs. It reconciles proposed changes against state modules and dependencies, clearly marking MVP, deferred, or blocked work to avoid missed dependencies.

To mark MVP and deferred work in feature plans, apply the proposed feature to app constraints and MVP scope. The plan must explicitly categorize work items as MVP, deferred, or blocked while cross-referencing the relevant state modules and components.

Feature planning requires a current app spec, architecture, and glossary to ground the proposed changes. Without these foundational planning docs, the process cannot accurately map dependencies or reconcile constraints against the existing state modules.

When feature planning misses dependencies, it typically means the plan was not applied to the current app constraints and dependency mapping across spec, glossary, and planning docs. Ensuring explicit references to state modules and components resolves this.