diagnose
Skill0 starsChanged 8 months agoApache-2.0View on GitHub
Investigate a bug report — find root cause, trace it up the SDD authority chain, and auto-fix if the problem is within autonomous layers (specification and below). Use when given a bug description, error report, or failing test.
193 other projects use a version of this.
Adopted by
Most recently taken up by
- blauwtje/exotheir own version, first seen Nov 16, 2026
- Robo-Co-op/robobuilder-standardtheir own version, first seen Nov 16, 2026
- akshay-diwadkar/first-four-hourstheir own version, first seen Nov 16, 2026
- AshrafDurjoy/genai-shared-patternstheir own version, first seen Nov 16, 2026
- FAHTHIZ/oasistheir own version, first seen Nov 16, 2026
- timmo001/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use zoom-out, to-prd 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.
victorgarciaesgiSkillzoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
Also in 61 projects that use this
GoogleSkillto-prd
Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Also in 56 projects that use this
GoogleSkillto-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
Also in 53 projects that use this
simo97Skilledit-article
The user will invoke this skill to help them edit an article.
Also in 17 projects that use this
simo97Skillwrite-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
Also in 44 projects that use this
AnasX7Skillsetup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
Also in 27 projects that use this
- +4 more from simo97
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- github/awesome-copilot★ 41ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
- CherryHQ/cherry-studio-app★ 4.1ksame name
- pedrohcgs/claude-code-my-workflow★ 1.7ksame name
- formancehq/ledger★ 1.5ksame name
- getagentseal/founder-playbook★ 745same name
- victorgarciaesgi/regle★ 508same name
- amazingloft999-droid/mattpocock-skills★ 422same name
- openvetta/open-vetta★ 299same name
183 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
- sddSkill
- triageSkill
- writing-architectureSkill
- writing-specsSkill
- writing-tasksSkill
- writing-testsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 9 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
When the agent returns, summarize the root cause in 2-3 sentences with specific file:line references.
- Distinctive: line 22
Read each layer's documents to find the highest layer that needs correction.
- Very specific: line 24
Read the specification that governs this behavior (in specification/).
- Very specific: line 28
If the spec appears wrong or incomplete, read the parent architecture document (in doc/architecture/).
- Very specific: line 32
If the architecture appears wrong, read the feature document (in doc/features/).
- Very specific: line 35
If the feature doc appears wrong, read the PRD (in doc/requirements/).
- Distinctive: line 53
Read the parent architecture document.
- Very specific: line 55
If a problem is identified with the architecture while fixing the spec, write a detailed description to doc/architecture/feedback/ and stop.
- Distinctive: line 61
Write failing tests first, then implement until tests pass.
- Very specific: line 63
Read the blast radius from $CLAUDE_PROJECT_DIR/sdd-blast-radius if it exists.
- Distinctive: line 65
Write or update tests that reproduce the bug or cover the spec change within the blast radius.
- Distinctive: line 66
Do not change specifications.
- Very specific: line 67
Run python -m pytest test/ -x -q.
- Distinctive: line 69
Write the implementation to make tests pass.
- Very specific: line 70
Run python -m pytest test/ -x -q after each significant change.
- Very specific: line 80
Write to doc/architecture/feedback/, notify the user, and stop.
- Very specific: line 86
Remove $CLAUDE_PROJECT_DIR/sdd-blast-radius if it exists.
- Very specific: line 87
Check off completed tasks in tasks/ (update - [ ] to - [x]).
- Distinctive: line 88
If any feedback files still exist, notify the user and stop.
- Distinctive: line 103
Do not make a PR — the user decides when the branch is ready.
“Common” is measured: kept by at least 6 in 10 of the 175 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
Diagnose a bug and triage it to the correct SDD layer: $ARGUMENTS
Phase 1: Find the root cause
Delegate the investigation to an Explore subagent to keep the main context clean.
- Launch an Explore agent with this prompt:
- The bug description from the user
- "Search the codebase for the relevant code paths. Trace the call chain to find where the behavior diverges. Check handlers, validation, tests. Return: the root cause (file, function, line, why), and which source/test/spec files are involved."
- When the agent returns, summarize the root cause in 2-3 sentences with specific file:line references.
Phase 2: Triage up the authority chain
Read each layer's documents to find the highest layer that needs correction. Only read the specific documents relevant to the bug — do not read broadly.
- Read the specification that governs this behavior (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?
- 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 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?
- If the feature doc appears wrong, read the PRD (in
doc/requirements/). Ask:- Is the requirement clearly stated?
Phase 3: Decide and act
Determine the highest affected layer from the triage. Do NOT present a report table yet — act first, report at the end.
If the fix requires changes to
doc/layers (requirements, features, or architecture):- These require human approval. Present the triage table (same format as step 29), then present 2-3 options with critical analysis and a recommendation. Wait for the user to decide before proceeding. Stop here.
If the fix starts at
specification/or below (all doc/ layers are OK):- This is within autonomous scope. Do not wait for user approval. Proceed directly to Phase 4.
Phase 4: Fix the specification (if needed)
Skip this phase if the specification is correct (the bug is purely an implementation deviation). Go directly to Phase 5.
- Run:
echo "specification" > $CLAUDE_PROJECT_DIR/sdd-layer - Read the parent architecture document.
- Fix the specification gap or error in
specification/. - If a problem is identified with the architecture while fixing the spec, write a detailed description to
doc/architecture/feedback/and stop. Notify the user — architecture changes require human approval. - Record the blast radius — write changed spec filenames to
$CLAUDE_PROJECT_DIR/sdd-blast-radius:echo "specification/channels.md specification/storage.md" > $CLAUDE_PROJECT_DIR/sdd-blast-radius
Phase 5: Tests and implementation (TDD)
Write failing tests first, then implement until tests pass. Track feedback cycles (any return to an earlier step from a feedback resolution counts as one cycle).
- Read the blast radius from
$CLAUDE_PROJECT_DIR/sdd-blast-radiusif it exists. - Run:
echo "tests" > $CLAUDE_PROJECT_DIR/sdd-layer - Write or update tests that reproduce the bug or cover the spec change within the blast radius.
- Do not change specifications. If a spec problem is found, go to step 21.
- Run
python -m pytest test/ -x -q. New tests covering the change should fail. Existing tests may pass or fail. - Run:
echo "implementation" > $CLAUDE_PROJECT_DIR/sdd-layer - Write the implementation to make tests pass. Do not change tests or specifications.
- Run
python -m pytest test/ -x -qafter each significant change. When all tests pass, proceed to Phase 6. - If a spec problem is found (during tests or implementation):
- Run:
echo "specification" > $CLAUDE_PROJECT_DIR/sdd-layer - Fix the specification. Delete the feedback file.
- Increment feedback cycle count. Return to step 14.
- Run:
- If a test problem is found (during implementation):
- Run:
echo "tests" > $CLAUDE_PROJECT_DIR/sdd-layer - Fix the test. Delete the feedback file.
- Increment feedback cycle count. Return to step 18.
- Run:
- If an architecture problem is found:
- Write to
doc/architecture/feedback/, notify the user, and stop.
- Write to
- After 3 feedback cycles, stop and present the situation to the user: summarize what was attempted, what keeps failing, and ask for direction.
Phase 6: Completion
- Run:
echo "free" > $CLAUDE_PROJECT_DIR/sdd-layer - Remove
$CLAUDE_PROJECT_DIR/sdd-blast-radiusif it exists. - Check off completed tasks in
tasks/(update- [ ]to- [x]). - If any feedback files still exist, notify the user and stop.
- Present the triage table:
Root cause: <2-3 sentence summary with specific file:line references>
| 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 |
- Report what was done and which files were changed.
- Do not make a PR — the user decides when the branch is ready.
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.

