Grit-77/done-is-a-claim

English · Türkçe
Replay stamp · Static cover
Your agent says “done”. What would prove it?
An evidence-first development workflow for coding agents: understand → plan →
implement → diagnose → review → verify → deliver. 15 connected skills, 18
incident-backed rules, and optional tools that keep the evidence attached to the
work it tested. Small tasks take a shorter path.
Get started · Use in your project · Follow the workflow · Choose a skill · Try the demo
## Get started
Recommended first use: one small task in a project you already have.
1. Install with your coding agent. Give it this request:
> Install https://github.com/Grit-77/done-is-a-claim. Follow INSTALL.md, preserve
> my existing instructions and settings, verify the installation, and explain
> what changed and how I start using it. Use my current account and permissions.
For the installing agent: follow INSTALL.md. Identify the
current host and installation scope, preserve existing work, verify the result,
and finish with a short explanation in the user's language.
2. Open a fresh session in your project and choose a small task. Include
your actual bug or change request, then add:
> Use using-done-is-a-claim for this task. Before editing, identify the observable
> result and the check that can test it. Take a proportionate path through the
> work and review. Report the actual result, tested inputs and remaining gaps.
> Continue within my existing authorization.
3. Inspect the result, then tell us what happened. Can you identify the
check that ran, what it established, and anything still unverified? If the
skill did not load or the check could not run, keep that visible. For an optional
saved command receipt, follow the existing-project guide.
Share a first-use report:
include your client, release or revision, task, observed result and uncertainty.
A failure or confusing step is useful feedback too. Remove private information
before sharing. Installing instructions does not enforce agent compliance.
### Manual installation
Install all skills as a native plugin:
Claude Code
bash
claude plugin marketplace add Grit-77/done-is-a-claim --scope local
claude plugin install done-is-a-claim@done-is-a-claim-marketplace --scope local
Codex
bash
codex plugin marketplace add Grit-77/done-is-a-claim
codex plugin add done-is-a-claim@done-is-a-claim-marketplace
Start a fresh session. In Claude Code, invoke
/done-is-a-claim:using-done-is-a-claim; in Codex, select
using-done-is-a-claim through /skills or the $ skill picker.
Plugin scope, updates and validation limits →
Prefer project-local copies or the rules alone? Use a toolkit clone:
| You use | Add to your project |
| Codex or an agent that reads AGENTS.md | Copy AGENTS.md to the project root. |
| Claude Code | Copy AGENTS.md and CLAUDE.md, which imports it with @AGENTS.md. |
| Existing instructions | Merge the relevant rules into your file. Keep your project-specific commands and constraints. |
You can start with that one rules file. Native plugin installation does not add
these rules to the adopting project's instructions.
Installation options on macOS, Linux or Windows →
Want the workflow in your project without overwriting existing files? From this clone,