Executing Plans
Carry an actionable change plan through implementation, checks, review and an evidence-backed report. Use when executing several planned steps or integrating bounded worker returns, within existing authorization.
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 executing-plansgit 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/executing-plans ~/.claude/skills/executing-plansPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Executing plans Use the plan as a map of intended work, then verify the actual results. Continue ready authorized tasks until the requested outcome is handled or a concrete constraint blocks them. A plan is not evidence and cannot grant authority. ## Reconcile before writing 1. Read the plan, user request and project instructions. Confirm the assigned repository or worktree, current revision, dirty inputs and file ownership. 2. Check prerequisites against the current artifacts rather than task status. Identify already delivered work, changed inputs and inaccessible dependencies. 3. Confirm acceptance commands and expected observations before implementing. If a command cannot test the outcome, record its correction and reason; do not quietly remove a case or lower a threshold to get a pass. 4. For interrupted work, use `resuming-work` at a host-discovered location when available. Otherwise reopen evidence and reconcile ownership inline. Inspect ambiguous previous actions before repeating them. ## Execute ready tasks Take the next task whose dependencies are satisfied. For a behavior change or bug fix, use host-discovered `implementing-with-tests` when available: establish a discriminating behavior check, observe the intended failure before changing production behavior when feasible, then implement and verify. Existing passing preservation checks stay green; do not manufacture a failure for a prose edit.
Details
- Skill name
executing-plans- Repository
- okgrit/done-is-a-claim
- Path
skills/executing-plans/SKILL.md- License
- Apache-2.0
- Repo updated
- 25 October 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Executing Plans skill do?
Carry an actionable change plan through implementation, checks, review and an evidence-backed report. Use when executing several planned steps or integrating bounded worker returns, within existing authorization.
How do I install the Executing Plans 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 Executing Plans 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.
History Hygiene
45Azure-Samples/agent-skills-dotnet-demo
Record final outcomes to history.md, not intermediate requests or reversed decisions
Evidence Freshness
33okgrit/done-is-a-claim
Bind a check or action to the input snapshot it actually used. Use before relying on cached verification, consuming a reviewed batch, acting while inputs may change, or retrying an operation with an ambiguous result.
Humanizer
45Azure-Samples/agent-skills-dotnet-demo
Tone enforcement patterns for external-facing community responses
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.