debt
Skill2 starsChanged 4 months agoLicence not identifiedView on GitHub
Durable deferred-fix technical-debt register — the sink for CLAUDE.md §C-surfaced findings: concrete, located, out-of-scope defects noticed DURING development that must be "surfaced, not fixed." CAPTURE (`/debt capture`): the main loop or user records a REAL observed defect — located, with a falsifiable done_when — into `.orchestrate/debt/open/`; a capture that cannot meet the bar FAILS LOUD rather than storing a placeholder. LIST (`/debt list`): a severity-ordered VIEW of the open register, filterable by category/area — never a second sink. FIX (`/debt fix`): the thin diagnose → staleness-reverify → route-each-fix-to-`orchestrate` → verify-closure loop; debt NEVER builds inline and names no agent, play, or cast. CLOSE (`/debt close`): honest won't-fix / already-resolved, with a required, re-verified reason. Use when a noticed-but-out-of-scope defect must be deferred for later ("add this to the debt register", "capture this as tech debt", "what's in the debt backlog", "work down the debt findings", "triage and fix the deferred findings"). Its finding-source is ad-hoc human/agent observation of out-of-scope defects noticed during development — it diagnoses, routes, and verifies while `orchestrate` fixes.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- PeterPartridge/CooperativeAICodingtheir own version, first seen Nov 8, 2026
- MagicJosh/rastheir own version, first seen Oct 15, 2026
- dimitritholen/1337-claudetheir own version, first seen Sep 23, 2026
- AGMO-Inc/agmo-everywheretheir own version, first seen Mar 18, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- AGMO-Inc/agmo-everywhere★ 4same name
- PeterPartridge/CooperativeAICoding★ 2same name
- MagicJosh/ras★ 1same name
- dimitritholen/1337-claude★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- handoffSkill
- orchestrateSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.