Turn recurring failures into fixes developers can find.
troubleshooting documentation
Produces evidence-ranked troubleshooting entries, verification logs, and wiring plans for recurring developer failures.
When to use it
Use for troubleshooting documentation, error-code references, known-issues pages, or recurring support questions, but not live-incident debugging.
Give it failure-signal exports; it interviews you, presents a ranked queue for agreement, then writes and verifies the selected documentation.
What you provide
This skill
retrieval index
Triggers retrieval re-embedding
persistent memory
Stores durable project decisions
No setup requirements listed in the analysis.