implementation-planner

Break down implementation tasks by analyzing your codebase and dependencies, then generate a numbered plan with file:line references, prerequisites, and verification steps. This approach ensures concrete, sequenced work from initial analysis through delivery and testing.

An implementation plan should include numbered, ordered tasks with file and function references, test-first steps, automated and manual verification checkpoints, and cleanup documentation. This structure makes the plan executable and tracks progress against functional requirements.

Yes. Task breakdown planning applies to feature implementation, refactors, and bug fixes by analyzing codebase context and dependencies, spawning parallel research when needed, and sequencing work so prerequisites complete before dependent tasks begin.

Codebase analysis identifies file dependencies, function signatures, and related documents before planning begins, enabling deterministic task sequencing. This context prevents planning steps that conflict with existing code structure or miss required integration points.

A task plan includes file:line references, test-first steps, verification procedures, and documented prerequisites and cleanup—making it executable and auditable. A to-do list typically lacks this structural detail, making progress harder to track against functional requirements.

Spawn parallel research tasks when planning reveals unknown dependencies, undocumented code sections, or unclear integration points. This prevents blocking the full plan and surfaces context needed to sequence remaining work accurately.