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.

janjaszczak Updated

File contents

plan-as-contract

Activation gate

Use if:

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

Procedure

  1. 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.
  2. Define objective + acceptance criteria (testable).
  3. Enumerate touched areas: BE/FE/DB/config/CI/CD/infra (or explicitly “NOT touched”).
  4. Identify dependencies (APIs, flags, secrets, external services).
  5. Provide ordered steps with file paths and validation commands.
  6. Stop: wait for user approval (unless user asked “just do it”).

Output

  • Plan (steps) + Risks + Verification checklist.

janjaszczak/cursor/tree/main/skills/plan-as-contract commit 5d2af6df81

Frequently asked questions

npx skillmds@latest add janjaszczak/plan-as-contract