skills.rest
thewoolleyman
thewoolleymanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

livespec-doctor

Runs livespec doctor checks against a spec tree and surfaces findings as JSON or dialogue.

Updated Aug 15, 2026
Search Tags:#spec-driven development#doctor#spec validation#invariant checks#cli dispatch#livespec#pi runtime
One-click install
npx skills add https://github.com/thewoolleyman/livespec-driver-pi --skill livespec-doctor-thewoolleyman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: livespec-doctor
Source: https://github.com/thewoolleyman/livespec-driver-pi/tree/main/skills/livespec-doctor
Command: npx skills add https://github.com/thewoolleyman/livespec-driver-pi --skill livespec-doctor-thewoolleyman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It validates a livespec specification tree for structural and semantic problems by running the doctor operation's static, objective, and subjective check phases, so spec invariant violations are found before they propagate. ## Core Features & Use Cases - Static structural checks: Invokes the config-named doctor CLI (default doctor_static.py from livespec core) to detect structural failures in the spec tree. - LLM-driven objective and subjective phases: Extends beyond static checks with deeper analysis, surfacing each finding as JSON or as a per-finding user dialogue. - Post-step integration: Runs as the closing phase of every wrapper-having livespec operation (propose-change, revise, and others). - Use Case: After revising a governed project's SPECIFICATION directory, ask the agent to run livespec doctor to confirm no invariants were broken before committing. ## Quick Start Ask the agent to run livespec doctor against this project's spec tree and show me any findings.

Frequently Asked Questions about livespec-doctor

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

FAQPage Schema
How do I run livespec doctor on my spec tree?▼

Invoke the /skill:livespec-doctor binding in a pi session. It resolves the livespec core root, reads core's doctor prose, then runs the doctor CLI named in your project's .livespec.jsonc, defaulting to doctor_static.py.

What checks does livespec doctor perform?▼

It runs three phases: a static phase detecting structural failures, plus LLM-driven objective and subjective phases. Findings are surfaced as JSON or through a per-finding dialogue with the user.

Does livespec doctor modify my specification files?▼

No, the doctor operation is read-only. It only inspects the spec tree and reports findings; changes are made through separate operations like propose-change and revise.

Why does livespec doctor fail silently in non-interactive pi runs?▼

Pi's project-trust gate silently ignores project-local packages under non-interactive invocations like pi -p until a trust decision exists. Establish trust via trust.json, defaultProjectTrust, or a per-run --approve flag.

Can I override the doctor CLI that livespec uses?▼

Yes. The governed project's .livespec.jsonc names the doctor CLI under spec_clis.doctor as an argv array. If absent, the binding falls back to core's reference default, doctor_static.py.

Related Skills

Explore More Software Engineering Skills→
davidorexdavidorex
25

pi-project-workflows

Install a meta-package re-exporting pi-project, pi-workflows, and pi-behavior-monitors.

Community
Intermediate
davidabeyerdavidabeyer
13

revise

Revise project plans and specifications based on critique findings.

Official
Advanced
tale-projecttale-project
20

review

Automate adversarial code reviews and orchestrate built-in verification for pull requests.

Official
Advanced
bbvch-aibbvch-ai
9

implement-feedback-from-pr

Implements GitHub PR review feedback for the aihub-core monorepo with lint and tests.

Official
Advanced