JordanGunn/nunchuck / skills/doctor
doctor
VerifiedDiagnoses software failures by combining deterministic evidence gathering with agent judgment. Models failures as medical cases. Idempotent — run repeatedly until confident diagnosis, then generate schema-based treatment.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 5.7 KB |
| SKILL.md | skill md | 640 B |
| assets/schemas/session.schema.yaml | config | 1.7 KB |
| assets/schemas/treatment.schema.yaml | config | 1.4 KB |
| references/00_ROUTER.md | markdown | 1.6 KB |
| references/01_SUMMARY.md | markdown | 1.3 KB |
| references/02_TRIGGERS.md | markdown | 1.0 KB |
| references/03_ALWAYS.md | markdown | 1.1 KB |
| references/04_NEVER.md | markdown | 1.1 KB |
| references/05_PROCEDURE.md | markdown | 2.1 KB |
| references/06_FAILURES.md | markdown | 1.9 KB |
| scripts/include/.doctor/session.yaml | config | 236 B |
| scripts/include/doctor_cli.py | script | 11.2 KB |
| scripts/include/doctor_parse.py | script | 10.7 KB |
| scripts/include/pyproject.toml | manifest | 236 B |
| scripts/router_checks.shexecutable | script | 1.7 KB |
| scripts/skill.ps1 | script | 1.5 KB |
| scripts/skill.shexecutable | script | 1.2 KB |
references/05_PROCEDURE.md
View on GitHub---
description: Canonical execution path for this skill.
index:
- Step 1: Initialize Session
- Step 2: Record Symptoms
- Step 3: Surface Scan
- Step 4: Parameterized Evidence Gathering
- Step 5: Form Hypotheses
- Step 6: Iterate
- Step 7: Diagnose
- Step 8: Generate Treatment
- Step 9: Handoff
---
# Procedure
Canonical execution path for the doctor skill.
## Step 1: Initialize Session
```bash
./skill.sh init --patient "system-name"
./skill.sh status
```
Creates `.doctor/session.yaml` with `status: investigating`.
## Step 2: Record Symptoms
For each symptom the user describes:
```bash
./skill.sh symptom "API returns 500 error" --category error --evidence "logs show timeout"
```
## Step 3: Surface Scan
Identify relevant file landscape:
```bash
./skill.sh surface --patterns "*.py" "*.yaml" --path src/
```
## Step 4: Parameterized Evidence Gathering
Agent chooses search terms based on symptoms:
```bash
./skill.sh grep "connection timeout" --save
./skill.sh grep "database pool" --type py --save
```
**Key pattern:** Agent provides subjective terms → Script returns deterministic matches.
## Step 5: Form Hypotheses
Based on evidence, record hypotheses with confidence:
```bash
./skill.sh hypothesize "Database connection pool exhaustion" --confidence 65 --falsifiable "Pool metrics show available connections"
```
## Step 6: Iterate
Repeat Steps 4-5 until one hypothesis reaches sufficient confidence (typically >80%).
Check status:
```bash
./skill.sh status
```
## Step 7: Diagnose
When confident, set diagnosis:
```bash
./skill.sh diagnose "Connection pool exhaustion under load" --confidence 85 --cause "Pool size too small for traffic"
```
## Step 8: Generate Treatment
Produce schema-based treatment plan:
```bash
./skill.sh treat --option "Increase pool size:Set pool_size=50:low" --option "Add connection retry:Implement exponential backoff:medium" --recommend "Increase pool size"
```
Generates `.doctor/treatment.md`.
## Step 9: Handoff
Present treatment plan to user. Skill complete.
To clean up after treatment is accepted:
```bash
./skill.sh clean
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |