plan-as-contract
Activation gate
Use if:
- •Multi-file changes, migrations, security/perf sensitive work, or irreversible ops.
Procedure
- •Define objective + acceptance criteria (testable).
- •Enumerate touched areas: BE/FE/DB/config/CI/CD/infra (or explicitly “NOT touched”).
- •Identify dependencies (APIs, flags, secrets, external services).
- •Provide ordered steps with file paths and validation commands.
- •Stop: wait for user approval (unless user asked “just do it”).
Output
- •Plan (steps) + Risks + Verification checklist.