Implementation Planning

Overview

Write comprehensive implementation plans assuming the engineer is skilled but unfamiliar with the codebase and project conventions. Document everything they need: which files to touch for each task, complete code examples, testing commands, documentation to reference, and verification steps. Break work into atomic, committable units following DRY, YAGNI, and TDD principles.

Announce at start: "I'm using the implementation-planning skill to create the implementation plan."

Context: Plans should be created in a dedicated worktree for isolation.

Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md

When to Use