Menu
Use when something is broken, failing, or not behaving as expected (any domain - software, gadget, process, plan)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.
Use when the user wants to capture a repeatable task as a reusable spell, or asks "how do I build a workflow / skill / framework for X"
Use when the meta-builder routes to kind=subagent. Generates a spell that dispatches one or more subagents to do work in parallel or in isolation.
Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).
Use when browsing what spells are available - bundled seeds, your personal library, or both. Filter by kind, audience, or update status.
| name | troubleshooting-whats-not-working |
| description | Use when something is broken, failing, or not behaving as expected (any domain - software, gadget, process, plan) |
| kind | workflow |
| audience | anyone |
| ai-tools | any |
| complexity | guided |
| time | 10-30 min |
| version | 1.0.0 |
| source | bundled |
Walks you from "something is wrong" to a verified diagnosis using evidence, not guesses. Works for software bugs, broken appliances, stalled projects, or interpersonal issues.
A diagnosis (the cause) plus a verified fix attempt or, if unfixable yet, a clear "next thing to test."
This is a guided workflow.
Write one sentence: "When X, I expect Y, but I get Z." If you can't write this sentence, the symptom isn't precise enough yet. Sharpen.
What changed since this last worked? Be specific: "I updated the app" or "we moved offices" or "she started a new job." If "nothing changed," challenge that — something always did.
Find the smallest scenario that still produces the symptom. Strip away anything optional. The smaller the failing case, the easier the cause is to see.
State: "I think the cause is X because of evidence Y." One hypothesis at a time.
Design a check that would prove the hypothesis wrong if it's wrong. Run the check. Record what you observed.
After fixing: reproduce the original symptom scenario. The symptom must be gone. Otherwise the fix didn't fix it (despite what you'd like to believe).
Return to Stage 4 when a hypothesis is disproved. Return to Stage 1 when bisection reveals the symptom statement was wrong.
Input: My monthly invoice automation worked all year, last week it sent invoices to the wrong customers.
