writing-plans

Implementation planning decomposes a feature spec into bite-sized, file-level edit mapping and task sequencing. It maps exact files to create or modify, assigning responsibilities to keep changes reliable and reviewable.

Task decomposition for TDD structures work into bite-sized steps: write tests, verify failure, implement code, verify pass, then commit. This sequencing supports dependable progress and checkpoint test runs throughout the engineering workflow.

File-focused decomposition maps exact files to create or modify, assigning responsibilities to keep changes reliable and reviewable. This supports multi-step software changes across a codebase with limited prior context.

Yes, the implementation plan structures work into bite-sized steps ending with git commits. Each step follows a TDD sequence of test, verify fail, implement, verify pass, and commit to support dependable progress.

Implementation planning converts ambiguous requirements into a step-by-step plan with exact code snippets and command examples. It produces DRY, YAGNI-aligned steps that a developer can follow without prior context.

Yes, the generated plan provides explicit handoff guidance for subagent-driven or inline execution approaches. It aligns with other engineering workflow skills to support dependable execution handoff.