Skip to content

JordanGunn/nunchuck / skills/doctor

doctor

Verified

Diagnoses 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.

references/03_ALWAYS.md

View on GitHub
---
description: Non-negotiable invariants for this skill.
index:
  - Evidence Rules
  - Session Rules
  - Uncertainty Rules
  - Artifact Rules
  - Scope Rules
---

# Always

Non-negotiable invariants for the doctor skill.

## Evidence Rules

- Always cite file paths and line numbers for claims
- Always use `./skill.sh grep` to gather evidence (parameterized determinism)
- Always save evidence with `--save` flag for traceability
- Always state confidence percentages for hypotheses

## Session Rules

- Always check session status before acting
- Always update session state after changes
- Always preserve previous evidence (append, don't overwrite)

## Uncertainty Rules

- Always acknowledge when multiple hypotheses remain viable
- Always state what would falsify the current hypothesis
- Always prefer "likely" over "definitely" until confidence > 90%

## Artifact Rules

- Always produce complete artifacts (no partial outputs)
- Always ensure artifacts are consumable by another agent
- Always store artifacts in `.doctor/`

## Scope Rules

- Always verify grep terms with user before broad searches
- Always prefer targeted searches over codebase-wide scans
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall