analyze

Verifies MySpec spec bundles for consistency and code-to-spec convergence with severity-ranked findings.

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/myspecs/claude-plugins --skill analyze-myspecs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/myspecs/claude-plugins/tree/main/plugins/myspec-mcp/skills/analyze
Command: npx skills add https://github.com/myspecs/claude-plugins --skill analyze-myspecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Spec-driven development drifts: requirements lose task coverage, code diverges from the approved spec, and constitution constraints get violated silently. This Skill audits a MySpec specification bundle read-only and reports exactly what is missing, contradictory, or unimplemented before those gaps reach production. ## Core Features & Use Cases - Spec Consistency Mode: Checks constitution alignment, requirement quality (EARS+ criteria, measurable NFR targets), solution completeness, task coverage, dependency cycles, and sizing across the bundle. - Convergence Mode: Compares the repository against the spec, classifying every requirement as implemented, partial, missing, contradicts, or unrequested, and detects checkbox drift and constitution drift. - Severity-Ranked Reporting: Produces a findings table (CRITICAL to LOW) plus a coverage matrix showing requirement-to-task and requirement-to-test traceability percentages. - Use Case: Before a milestone review, ask whether the code matches the spec; the Skill greps tests for requirement ids, reads the modules named in solution.md, and reports that 18 of 20 requirements have tasks with FR-014 and NFR-003 uncovered. ## Quick Start Ask the assistant to analyze the spec bundle for project X and check whether the code matches the spec.

Frequently Asked Questions about analyze

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

FAQPage Schema
How do I check if my code matches the specification?▼

Use convergence mode, which reads the modules named in solution.md, searches tests for requirement ids case-insensitively, and classifies each requirement as implemented, partial, missing, contradicts, or unrequested. It also reports test traceability percentages and checkbox drift.

How to audit a spec bundle for requirement coverage?▼

Run spec consistency mode, which verifies every functional requirement appears on at least one task's _Requirements:_ line, checks acceptance criteria follow EARS+ patterns, and scores coverage as the percentage of requirements with tasks. Uncovered functional requirements are flagged CRITICAL.

Does the analyze skill modify my spec or repository?▼

No, analysis is strictly read-only and never writes to the platform or repo. Remediation happens only after you approve it, and gap-filling is append-only: new convergence tasks are appended to tasks.md without editing or renumbering existing tasks.

What severity levels does spec analysis report?▼

Findings use four levels: CRITICAL for constitution conflicts, uncovered functional requirements, and code-spec contradictions; HIGH for missing acceptance criteria, dependency cycles, and unknown requirement references; MEDIUM for ambiguity and oversized tasks; LOW for style issues.

Why does analysis fail without the myspec MCP server?▼

The Skill reads bundle documents through MCP tools like list_projects and read_spec_file, which require the myspec MCP server connection. Run the setup skill first to sign in or configure an API token before analyzing.

When should I use spec consistency mode versus convergence mode?▼

Use spec consistency before implementation starts or after spec edits, since it only needs the bundle. Use convergence at milestone checkpoints or when resuming a repo, since it compares the bundle against actual code and tests.