Implementation Planning

Turn a chosen outcome into executable work. A small change may need only a short checklist; a cross-system migration may need a durable plan.

Workflow

1. Read the relevant repository instructions, current implementation, tests and supplied requirements. Record the target state and any important mismatch with the brief.
2. Define completion in observable terms: changed behavior, acceptance checks, relevant non-goals and authority boundaries.
3. Break work at useful integration or verification boundaries. Name affected paths/interfaces, prerequisites, expected result and a focused check for each unit.
4. Order dependencies; identify migrations, compatibility constraints, rollback limitations and external decisions. Separate blocking questions from assumptions that can be tested while progressing.
5. Include code only where an interface, algorithm or tricky constraint needs a concrete example. Do not write a speculative full implementation or invent line numbers before inspecting the source.
6. Review uncertainty and one-way doors. For a risky or unfamiliar area use a relevant independent review; reviewer count follows unresolved risk, not a fixed panel.
7. If execution is authorized, continue into implementation and verification. If asked only for a plan, deliver the plan and stop at that boundary. Worktrees and commits follow actual repository needs, not a planning prerequisite.

Handoff shape