doctor

Diagnoses Specture project structure and applies schema migrations via a Node script.

1|Updated May 1, 2026
One-click install
npx skills add https://github.com/FerEscobarDev/Specture --skill doctor-ferescobardev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/FerEscobarDev/Specture/tree/main/skills/doctor
Command: npx skills add https://github.com/FerEscobarDev/Specture --skill doctor-ferescobardev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Projects using the Specture framework drift out of sync with the installed plugin version: broken documentation paths, stale configuration keys, missing state files, and pending schema migrations accumulate silently. This Skill mechanically audits the project's documentation corpus and structure, then applies safe migrations so the project matches what the plugin expects. ## Core Features & Use Cases - Corpus and structure linting (check mode): Detects broken paths, duplicate ADRs, unresolved placeholders, stale state seals, rules file issues, and pending schema migrations, reporting everything in a severity table without modifying anything. - Three-tier migration handling (migrate mode): Applies mechanical migrations automatically with verification and logging, drafts assisted migrations through Plan mode for user approval, and defers content migrations to their owning skills with exact commands. - CI-ready sync mode: Combines mechanical migration application with a full check, exiting with an error code on any ERROR so pipelines and the start router can gate on project health. - Use Case: After upgrading the Specture plugin, run the doctor to discover that your project is two schema versions behind; it applies the mechanical migrations, walks you through the assisted ones in Plan mode, and hands you the exact command for the content migration owned by another skill. ## Quick Start Ask the assistant to run the Specture doctor in check mode to audit the project structure and list any pending migrations.

Frequently Asked Questions about doctor

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

FAQPage Schema
How do I check my Specture project structure for problems?▼

Run the doctor in check mode, which executes the doctor.js script against your project root. It lints the documentation corpus, requirements, rules file, and state, then prints a severity table with suggested actions without modifying anything.

How do I migrate a Specture project after upgrading the plugin?▼

Run the doctor in migrate mode. It first does a dry run, then applies mechanical migrations with --apply, drafts assisted migrations in Plan mode for your approval, and defers content migrations to their owning skills with the exact command to run.

What are the requirements to run the Specture doctor?▼

The doctor requires Node.js version 22 or later on the PATH and an existing .specture/stack.yml file in the project. If stack.yml is missing, the doctor routes you to setup instead, since there is nothing to diagnose.

Can the Specture doctor run in CI pipelines?▼

Yes, sync mode is designed for CI and the start router. It applies mechanical migrations only, runs the full check, and exits with code 1 on any ERROR, while assisted and content migrations are only listed.

Does the doctor modify specs, reviews, or debug logs during migration?▼

No, migrations never touch completed specs, reviews, or debug logs. Content migrations that require judgment over user documents are never applied inline; they are deferred to their owning skills with Plan-mode approval.