janjaszczak/cursor

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.

First seen Feb 21, 2026

Installation

$ npx skills add janjaszczak/cursor --skill plan-as-contract

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from janjaszczak/cursor · top by installs.

npx skills add janjaszczak/cursor

Browse all from janjaszczak/cursor

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

CompatibilityWorks best with Cursor Plan Mode and ability to reference repo files.
Allowed toolsRead FileSearch(*)
Declared agents cursor
More metadata
intent
Use when approval gates reduce risk and rework.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,135 B
  • docs SUMMARY.md 194 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 7 installs

SKILL.md

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.