plan-as-contract

Produce a reviewable, file-referenced implementation plan that acts as a contract before execution. Use for risky ops, architecture changes, migrations, multi-file edits.

plan-as-contract

Activation gate

Use if:

Multi-file changes, migrations, security/perf sensitive work, or irreversible ops.

Procedure

If requirements are unclear or acceptance criteria are missing: ask 2–5 clarifying questions (scope, constraints, verify commands) before drafting the plan. Do not assume.
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.