swe-planner

To generate an implementation plan, theSkill analyzes your architectural design and breaks it down into atomic subtasks. It defines execution order, dependencies, and quality gates, then saves the detailed roadmap into a persistent `.plan/` tracking file within your repository.

Task decomposition is the process of breaking down complex architectural designs into manageable, atomic, and testable subtasks. This approach defines specific execution orders, maps dependencies, and creates clear quality gates to guide development workflows.

You can track implementation plan progress using persistent `.plan/` tracking files created within your repository. These files manage ongoing development workflows by monitoring subtask completion, dependencies, and quality gates throughout the project lifecycle.

Yes, you can use this to plan new features by generating subtasks that explicitly detail which files to modify and which tests to write. It transforms architectural structures into actionable steps like implementing a specific service or designing a database schema.

No external project management dependencies are required for task decomposition. The Skill operates independently to generate detailed software development plans, map dependencies, and create `.plan/` tracking files directly within your existing repository environment.

You need an agile implementation plan after an architect defines a new feature's structure and before coding begins. It bridges high-level architecture and actual development by defining testable subtasks, execution order, and quality gates for clear project roadmaps.