Planning Changes
Prepare a compact, executable plan for a substantial change with acceptance, file ownership, dependencies and expected observations. Use when several steps or collaborators need coordination; tiny clear edits can proceed directly.
Install
/plugin marketplace add okgrit/done-is-a-claimThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add okgrit/done-is-a-claim --skill planning-changesgit clone --depth 1 https://github.com/okgrit/done-is-a-claim.git /tmp/done-is-a-claim
mkdir -p ~/.claude/skills
cp -r /tmp/done-is-a-claim/skills/planning-changes ~/.claude/skills/planning-changesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Planning changes A plan connects the requested result to work someone can execute and verify. Keep it proportional to uncertainty and coordination. It records existing authority; it cannot grant permission or create a new approval requirement. ## Establish the boundary 1. Read the request and relevant project instructions. Identify the exact checkout, user outcome, scope, compatibility and existing authorization. 2. Inspect the relevant code and current diff. Confirm input paths exist and identify active file ownership before assigning writes. Record the base revision and dirty inputs that matter to this work. 3. Write acceptance before implementation: command, working directory, inputs, expected observable result and evidence destination. Name relevant broader checks and what they cannot establish. 4. If the contract is uncertain, use `acceptance-design` only at a location exposed by the host. Otherwise design a discriminating check inline. Correct an invalid contract explicitly, preserving the user's outcome. ## Make the smallest useful plan For an underspecified feature, start from the existing product and the user's desired outcome. Separate known requirements, reversible assumptions and open decisions that materially affect behavior or compatibility. Recommend a bounded approach with its tradeoff. Resolve consequential unknowns before dependent work; do not ask the user to supply details already available in the project or approve
Details
- Skill name
planning-changes- Repository
- okgrit/done-is-a-claim
- Path
skills/planning-changes/SKILL.md- License
- Apache-2.0
- Repo updated
- 25 October 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Planning Changes skill do?
Prepare a compact, executable plan for a substantial change with acceptance, file ownership, dependencies and expected observations. Use when several steps or collaborators need coordination; tiny clear edits can proceed directly.
How do I install the Planning Changes skill?
Claude Code plugin: /plugin marketplace add okgrit/done-is-a-claim. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Planning Changes popular?
It lives in okgrit/done-is-a-claim, which has 33 GitHub stars and 4 forks, and is included in 1 curated skill list.
Related skills
Acceptance Design
33okgrit/done-is-a-claim
Define executable acceptance for a bounded task before work or dispatch. Use when writing a worker brief, selecting success checks, or repairing an acceptance contract that cannot test the intended outcome.
Checking Delivery
33okgrit/done-is-a-claim
Verify an artifact at its actual delivery destination and distinguish send attempts, acknowledgements, publication and consumer checks. Use when reporting a file, message, export or deployment as delivered; creating a local draft alone does not imply delivery.
Collecting Worker Results
33okgrit/done-is-a-claim
Inspect a stopped worker's returned work and evidence before accepting it, retrying it or handing it to an integration owner. Use when a worker finishes, records disagree, or a green result has no visible change. Collection does not authorize merging.
Reviewer Protocol
45Azure-Samples/agent-skills-dotnet-demo
Reviewer rejection workflow and strict lockout semantics
Meeting Notes
45Azure-Samples/agent-skills-dotnet-demo
Summarize meeting transcripts into structured notes with action items. Use when asked to process, summarize, or extract action items from meetings.
Using Done Is a Claim
33okgrit/done-is-a-claim
Choose an evidence-first path for a development task, from acceptance through execution, review and completion. Use when starting substantive work or deciding the next step; clear tiny edits can proceed directly.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.