Using 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.

33 stars 4 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add okgrit/done-is-a-claim

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add okgrit/done-is-a-claim --skill using-done-is-a-claim
Manual install
git 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/using-done-is-a-claim ~/.claude/skills/using-done-is-a-claim

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Using Done is a claim

Turn the user's outcome into a bounded change and a report supported by current
observations. Scale the process to the task. This entry skill works on its own;
the optional routes below add depth when those skills are actually available.

## Establish the task

1. Identify the requested outcome, exact repository or worktree, existing
   authorization and owned files. Read applicable project instructions.
2. Confirm supplied inputs exist. For a requested new file, confirm its parent
   and intended role. Inspect the current revision and uncommitted changes.
3. Before editing, name the acceptance command and observable result, plus
   relevant broader checks. A prose change may need a structure check and
   direct reading rather than new tests. State any untestable boundary.
4. If the outcome or acceptance cannot distinguish success from a plausible
   failure, clarify that boundary before dependent work. Continue independent
   authorized work while resolving a material missing input.

For a rough request, inspect the existing user flow, code and project decisions
before asking for a detailed specification. Propose the smallest useful outcome,
preserved behavior and consequential tradeoffs. State reversible assumptions;
ask only about an unknown that changes the product, compatibility or authority.
Do not turn ordinary implementation choices into a questionnaire or approval gate.
Read the full skill on GitHub

Details

Skill name
using-done-is-a-claim
Path
skills/using-done-is-a-claim/SKILL.md
License
Apache-2.0
Repo updated
25 October 2026

FAQ

What does the Using Done Is a Claim skill do?

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.

How do I install the Using Done Is a Claim 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 Using Done Is a Claim 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

33

okgrit/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.

Testing & QAIn 1 list

Checking Delivery

33

okgrit/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.

DevOps & CloudIn 1 list

Collecting Worker Results

33

okgrit/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.

OtherIn 1 list

M365 Integration

52

korchard333/claude-power-platform-community

Microsoft 365 integration with Power Platform. Use when: Teams, SharePoint, Graph API, Outlook, Microsoft 365, M365, Copilot connector, Teams tab, Adaptive Cards, SharePoint lists, Graph queries, email templates, calendar integration.

Productivity & Notes

Reviewer Protocol

45

Azure-Samples/agent-skills-dotnet-demo

Reviewer rejection workflow and strict lockout semantics

Productivity & Notes11

File Todos

59

ratacat/claude-skills

This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.

Productivity & Notes10

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.