Menu

Individual skill

using-done-is-a-claim

0upvotes

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.

skills/using-done-is-a-claim/SKILL.md

Read pinned source

Source commit 14c75a97ccbcca4c11daca25a93c8f0da5ad70d1

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
33
Repository last updated
Oct 25, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top