plan-as-contract

Generate pre-execution contract plans for risky multi-file changes.

1|Updated Jan 15, 2026

Search Tags:#architecture #migrations #plan #risk-management #code-review #approval #contract

Ready to run

npx skills add https://github.com/janjaszczak/cursor --skill plan-as-contract

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-as-contract
Source: https://github.com/janjaszczak/cursor/tree/main/skills/plan-as-contract
Command: npx skills add https://github.com/janjaszczak/cursor --skill plan-as-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams prevent costly missteps by producing a formal, reviewable contract before risky changes are executed.

Core Features & Use Cases

Pre-execution contracts: Capture objective, acceptance criteria, and success metrics to gate changes.
Scope and dependency mapping: Enumerate touched areas (BE/FE/DB/infra), dependencies, and external APIs.
Verification readiness: Define validation steps and sign-off requirements to enable gated approvals.

Quick Start

Provide a concise plan document that catalogs objective, acceptance criteria, touched components, dependencies, and a step-by-step execution path for gated review.

Frequently Asked Questions about plan-as-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a pre-execution contract plan for risky architecture changes?▼

To create a pre-execution contract plan for architecture changes, you draft a document enumerating objectives, acceptance criteria, touched areas, dependencies, ordered steps, and verification checkpoints to enable gated approval.

What should be included in a migration plan to enable gated approval?▼

A migration plan for gated approval should include the objective, acceptance criteria, touched components across BE/FE/DB/infra, dependencies, external APIs, and a step-by-step execution path with validation checkpoints.

When do I need a formal contract plan for multi-service updates?▼

You need a formal contract plan for multi-service updates when dealing with risky, multi-file changes across repositories that require scope mapping, dependency enumeration, and verification readiness to prevent costly missteps.

How do I map dependencies and touched areas for a multi-file refactor?▼

You map dependencies and touched areas for a multi-file refactor by cataloging all affected backend, frontend, database, and infrastructure components, along with external APIs, to generate a comprehensive pre-execution contract.

Does this approach work for code review and risk management across repositories?▼

Yes, this approach works for code review and risk management by producing a formal, reviewable contract that defines success metrics, validation steps, and sign-off requirements before risky multi-repository changes are executed.