Writing Plans

Overview

Turn requirements into an executable plan with concrete files, tests, and verification. A good plan removes guesswork without pretending the implementation is already done.

Core principle: Every task should be specific enough that an engineer can execute it without inventing missing requirements.

When to Use

Use this skill when:

• The task spans multiple files, phases, or checks
• Requirements are stable enough to plan
• The work benefits from a written execution order

Do not use this skill when:

• The change is small enough to track directly in update_plan
• Requirements are still ambiguous
• The user asked to implement immediately and the work is trivial