goddard-app-sprint-planner

You can plan MVP-first app sprints by reading existing planning docs like sprints.md and feature-recommendations.md, classifying features as active MVP, deferred, or blocked, and placing them in the earliest sprint whose prerequisites exist.

Dependency-first MVP sprint planning is a method that maintains a rollout schedule grounded in existing planning docs, ensuring new features are only placed into a sprint when all prerequisite features have been completed.

When a feature moves, you update adjacent sprint goals and rationale by reading multiple plan sources, preserving existing sequencing rules, and adjusting related plan documents to reflect the new dependency assumptions.

You separate active, deferred, and blocked work in a project roadmap by classifying features according to whether their prerequisites exist, then documenting each classification with clear rationale in plan documents like sprints.md.

Yes, you can determine sprint composition by reading and referencing existing planning docs such as spec/app.md, best-practices.md, and glossary.md, which grounds sprint decisions in established plans rather than ad-hoc roadmaps.

Automated sprint plan rebalancing relies on existing planning docs and assumes dependency rules are already documented, meaning it cannot infer missing prerequisites or create new feature recommendations independently of the provided sources.