Durable Plan

Turn planning into durable repository documentation. The plan file, not the conversation, is the source of truth: it records the agreed scope, phased work, verification, completion state, handoff context, architectural decisions, and a deployment plan.

Do not execute deployments, publish releases, run production migrations, or make live-environment changes unless the user explicitly asks for that action. Writing a deployment plan is expected; performing the deployment is not.

1. Reach Shared Understanding First

Do not write the plan until the scope is fully understood. Interview the user relentlessly, using the grill-me pattern: