Implementation Planning

Write comprehensive implementation plans assuming the executor has zero context. Document everything: which files to touch, complete code, how to test. Bite-sized tasks. DRY. YAGNI. TDD.

The Iron Law

NO IMPLEMENTATION WITHOUT A PLAN FIRST

For multi-step tasks, write the plan before writing code.

When to Use

• MUST: Before implementing features with 3+ steps
• MUST: Before complex refactoring
• SHOULD: When multiple files need coordinated changes
• MAY: Skip for single-file, single-function changes