writing-plans

Implementation planning for multi-stage engineering tasks translates specs into actionable, bite-sized steps. It specifies exact files to modify, test commands, and commit guidance, allowing execution without prior codebase knowledge.

You can generate a TDD task breakdown by processing requirements through this Skill. It structures work into bite-sized steps adhering to DRY and YAGNI principles, providing concrete test commands and expected outcomes for each file modification.

Yes, generating implementation plans with exact file modifications and test commands is supported. The output provides repository-aware instructions, specifying files to create or modify alongside concrete command examples and expected outcomes for each task.

Yes, implementation planning works for developers with minimal codebase context by assuming low prior knowledge. It provides explicit file touch points, test strategies, and execution commands required to complete multi-stage engineering tasks without guessing.

The best way to structure multi-stage engineering tasks for subagent execution is saving the plan to a dated docs/plans path. This creates an execution-ready handoff enabling downstream sub-skills to implement the work task-by-task.

You should avoid using automated implementation planning for task breakdown when a change is not a multi-stage engineering task. It is designed for complex sequences requiring explicit test strategies and commit guidance, not simple, single-file edits.