Implementation Plan

Make one already-bounded Feature or child Task's internal execution strategy reviewable and recoverable when a concise approach preview is not enough.

Decide whether a plan is warranted

Create or update a plan when at least one material trigger exists:

• the user wants to review execution strategy before coding;
• implementation spans multiple meaningful slices whose stable intermediate states must remain recoverable;
• another session or collaborator needs more durable execution guidance than the task, spec, and design provide;
• modification or deployment order affects correctness;
• data, schema, protocol, or persisted-format migration is involved;
• compatibility must be maintained across versions or modules;
• rollout, feature flags, dual operation, or backout behavior matters;
• ownership spans modules or systems and coordination is non-obvious;
• verification must occur in a particular order to contain risk.

If none applies, return a concise approach preview covering change surface, execution order, material constraints, and verification seam, then stop. Create neither a plan artifact nor a skipped-plan marker, and do not begin implementation unless the user's current request separately assigns that exact Feature or Task.