triage
Skill0 starsChanged 8 months agoApache-2.0View on GitHub
Trace a known root cause up the SDD authority chain to determine which layer the fix should start at. Use when Claude has already identified a root cause and you need to determine the blast radius. Runs in an isolated context.
190 other projects use a version of this.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- bmtrnavsky/disciplined-vibe-codingtheir own version, first seen Nov 15, 2026
- oxc-project/oxctheir own version, first seen Nov 15, 2026
Used with
Projects with it also use writing-beats, setup-matt-pocock-skills and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 66 projects that use this
GoogleSkillsetup-matt-pocock-skills
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Also in 167 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 42 projects that use this
SethGammonSkillascii-diagram
Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.
Also in 4 projects that use this
simo97Skillmigrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Also in 68 projects that use this
LesaniSkillwriting-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
Also in 63 projects that use this
- +1 more from Lesani
Other versions190 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 190
- mattpocock/skills★ 325ksame name
- withastro/astro★ 64ksame name
- vectorize-io/hindsight★ 61ksame name
- ogulcancelik/herdr★ 47ksame name
- herdrdev/herdr★ 47ksame name
- colinhacks/zod★ 44ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- vercel-labs/skills★ 39ksame name
- vercel-labs/add-skill★ 39ksame name
180 more not listed
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 repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- specification/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- tasks/CLAUDE.mdCLAUDE.md
- test/CLAUDE.mdCLAUDE.md
- cleanupSkill
- diagnoseSkill
- sddSkill
- writing-architectureSkill
- writing-specsSkill
- writing-tasksSkill
- writing-testsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 179 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
If the spec appears wrong or incomplete, read the parent architecture document in doc/architecture/.
- Very specific: line 30
If the architecture appears wrong, read the feature document in doc/features/.
- Very specific: line 34
If the feature doc appears wrong, read the PRD in doc/requirements/.
- Distinctive: line 38
Stop at the highest layer where a problem is found.
“Common” is measured: kept by at least 6 in 10 of the 179 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.
Files
Triage a bug or failing test to determine which SDD layer the fix should start at: $ARGUMENTS
You have identified (or been given) a root cause. Before making any changes, trace it upward through the authority chain to find the highest layer that needs correction. Do NOT edit any files — this is a read-only audit.
Steps:
- Summarize the root cause in one sentence.
- Identify which implementation file(s) contain the bug. Read the relevant source in src/ and the corresponding test(s) in test/.
- Find the specification that governs this behavior. Read it in specification/. Ask:
- Does the spec correctly describe the expected behavior?
- Is the bug a deviation from the spec, or does the spec itself have a gap or error?
- If the spec appears wrong or incomplete, read the parent architecture document in doc/architecture/. Ask:
- Does the architecture correctly describe the design?
- Did the spec misinterpret the architecture, or is the architecture itself flawed?
- If the architecture appears wrong, read the feature document in doc/features/. Ask:
- Does the feature doc correctly capture what the system should do?
- Is the architecture inconsistent with the feature intent?
- If the feature doc appears wrong, read the PRD in doc/requirements/. Ask:
- Is the requirement clearly stated?
- Did the feature doc misinterpret the requirement?
Stop at the highest layer where a problem is found. Report your findings as a table:
Layer Document Status Finding Requirements doc/requirements/X.md OK / GAP / ERROR brief note Features doc/features/X.md OK / GAP / ERROR brief note Architecture doc/architecture/X.md OK / GAP / ERROR brief note Specification specification/X.md OK / GAP / ERROR brief note Tests test/X.py OK / GAP / ERROR brief note Implementation src/poule/X.py OK / GAP / ERROR brief note - Recommend which phase command to start with (e.g., "/specification", "/implementation") and briefly describe the fix at each affected layer, working top-down.
IMPORTANT: Do not make any edits. Only read files and report findings.
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.

