speckit-companion-doctor

Diagnose spec-kit run health by recomputing records, drift, and completion status.

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-companion-doctor-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-companion-doctor
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-companion-doctor
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-companion-doctor-luandopke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a spec-kit pipeline run goes wrong, it is hard to tell whether the record, the display, or the run's own claims are at fault. This Skill audits a spec's run health retroactively and read-only, surfacing unfinished steps, unjournaled tasks, step bleed, drift, and why completion never landed. ## Core Features & Use Cases - Run Health Audit: Recomputes checks for record integrity, triage disagreements, step bleed, drift, completion failures, template shape, and self-trace capture errors, always reporting ran/skipped/not-applicable status. - Drift Recomputation: Re-runs the drift computation instead of trusting prior verdicts, classifying flags as real, self-inflicted, suspect baseline, or unknown, and exposing false drift-clean claims. - Transcript Analysis: With the --chat flag, reads the AI session transcript for the run window to explain failed work, retries, and wasted effort. - Use Case: After a spec fails to reach completed status, run the doctor with --json to get a machine-readable report showing whether the completion write was refused, lost, or never attempted. ## Quick Start Ask the AI to run the companion doctor on the active spec and report which checks ran, which were skipped, and what findings explain why the run did not complete.

Frequently Asked Questions about speckit-companion-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check why a spec-kit run did not complete?▼

Run python3 .specify/extensions/companion/scripts/doctor.py from the repository root. The completion check reports whether the write was refused, reported success but never arrived, landed with a display disagreement, or was never attempted.

How to audit all specs in a repository at once?▼

Run the doctor script with the --all flag to sweep every spec in the repository. You can also target one spec with --feature-dir specs/<NNN>-<slug> or add --json for a machine-readable report.

Does the doctor modify files or stop the pipeline when it finds problems?▼

No. The doctor is read-only and never halts; it always exits 0. A check that crashes becomes that check's skip reason while the remaining checks still run, and fixing findings is a separate deliberate decision.

Can the doctor analyze specs created before it was installed?▼

Yes. Every core check derives from .spec-context.json and the spec's own documents, so it produces a meaningful retroactive verdict on specs created long before the command existed.

Why does the pipeline bar disagree with the step status?▼

The triage check resolves this into one of two verdicts: records disagree with each other, meaning a missing step-level complete blocks the stepper derived from history[], or records are consistent and the fault lies in the display.

What are the limitations of the --chat transcript audit?▼

The chat check is Claude-first and reads the AI session transcript for the run's recorded time window. On providers that keep no transcript it prints one line and exits successfully, and the transcript format is not a stable contract.