sp-writing-plans

To break down a software architecture design, you translate ambiguous proposals into a detailed task list with testable outcomes, mapping file structures and defining micro-tasks that take 2-5 minutes each. This ensures a clear implementation path and reduces rework risk.

The best way to plan test-driven development is to integrate the red, green, and refactor workflow directly into your planning phase. You define test coverage requirements alongside an implementation plan that generates atomic git commits for every completed task.

Yes, you can generate a file structure mapping before writing an implementation plan. The process outputs an IMPLEMENTATION_PLAN.md framework first, explicitly listing all files to be created or modified to ensure subsequent implementation steps are verifiable.

Yes, task management planning supports atomic commits for complex projects. It enforces a workflow where every completed micro-task produces a single git commit, ensuring all code changes remain trackable and safely reversible throughout the project.

Micro-tasks are used for software implementation instead of larger batches to enable rapid experimentation and iteration. By limiting each task to 2-5 minutes of work, you minimize inference errors, simplify test validation, and maintain strict atomic commit boundaries.

Limitations of automated implementation plans include built-in guardrails against placeholders and unsafe changes, meaning the generated task lists strictly require explicit design proposals as input and cannot operate effectively on entirely ambiguous or undefined requirements.