writing-plans

To create an implementation plan, use the skill to document required tasks, file touches, code, tests, and deployment steps. This provides a clear roadmap from tasks to artifacts, ensuring team alignment before coding begins.

Task decomposition in project management workflows involves breaking down multi-step requirements into specified tasks, artifacts, and checkpoints. This ensures planability and reusability across subsystems for engineering projects.

You need to write an implementation plan when you have a spec or requirements for a multi-step task. It articulates scope, files, tests, and docs across subsystems before engineers touch any code, ensuring zero context assumptions.

Yes, you can use this planning approach for TDD-oriented workflows. It supports brainstorming and planning by documenting file touches, required tests, and deployment steps to align teams on task scope and artifacts.

The best way to document file touches and deployment steps is to create a comprehensive implementation plan. It provides a clear roadmap from tasks to artifacts, ensuring engineers understand scope, tests, and docs across subsystems.

No, this implementation planning method assumes engineers have zero context and potentially questionable taste. It specifies required tasks, artifacts, and checkpoints to ensure planability and reusability without relying on prior knowledge.