sprint-planner

To generate a sprint plan, this skill analyzes your root TODO.md, architecture docs, and existing code to identify the next coherent scope. It then outputs a concrete plan file with exact file paths, tests, and execution order.

TDD-first development is enforced during sprint planning by sequencing tasks to ensure testable progression. The generated plan explicitly defines tests and acceptance criteria before implementation steps, maintaining strict test-driven workflows.

Yes, this sprint planner works for Django projects by enforcing Fat Model principles. It analyzes your architecture docs and code to generate sprint plans that specify exact class names and file paths aligned with your Django project structure.

The best way to structure executable sprint tasks is by consolidating project context into a markdown plan file. This skill defines explicit task sequencing, acceptance criteria, and exact execution order to reduce ambiguity and misalignment.

Yes, existing architecture docs are required to plan a coherent sprint scope. This skill relies on analyzing your architecture documents, root TODO.md, and current codebase to identify dependencies and generate a precise, executable plan.

Sprint planning lacks explicit file paths and execution order when project context is not consolidated. This skill resolves that by analyzing your TODO.md and architecture docs to output exact class names, file paths, and a strict execution sequence.