# plan

Purpose: Structure a task before starting so execution is deliberate, not exploratory.

1. Read the request carefully. Clarify ambiguities before proceeding.
2. Map the affected area — list files, modules, or services involved.
3. Read current state of the most relevant files.
4. Write a numbered step list. Each step is one atomic, reviewable change.
5. Flag risks: unknowns, breaking changes, external dependencies.
6. Present the plan and wait for user approval.

Do not write or modify code until the plan is approved.
