spec-analyze

Perform non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md. Use when user says "/spec-analyze", "analyze the spec", "check consistency" after /spec-tasks to identify issues before implementation.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "spec-analyze" with this command: npx skills add xfstudio/skills/xfstudio-skills-spec-analyze

Spec-Analyze

Cross-artifact consistency analysis - READ-ONLY, no file modifications.

Prerequisites: tasks.md must exist (run /spec-tasks first).

Workflow

  1. Initialize - Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks
  2. Load artifacts - spec.md, plan.md, tasks.md, constitution.md
  3. Build semantic models - Requirements inventory, task mapping
  4. Detection passes - 6 analysis categories
  5. Assign severity - CRITICAL/HIGH/MEDIUM/LOW
  6. Produce report - Markdown table with findings
  7. Offer remediation - Ask before any edits

Detection Categories

A. Duplication Detection

  • Near-duplicate requirements
  • Mark lower-quality for consolidation

B. Ambiguity Detection

  • Vague adjectives (fast, scalable, intuitive)
  • Unresolved placeholders (TODO, ???)

C. Underspecification

  • Verbs without measurable outcomes
  • Missing acceptance criteria
  • Tasks referencing undefined components

D. Constitution Alignment

  • MUST principle violations → CRITICAL
  • Missing mandated sections

E. Coverage Gaps

  • Requirements with zero tasks
  • Tasks with no mapped requirement
  • Non-functional requirements not in tasks

F. Inconsistency

  • Terminology drift
  • Missing data entities
  • Task ordering contradictions
  • Conflicting requirements

Severity Levels

LevelCriteria
CRITICALConstitution violation, missing core artifact, baseline blocker
HIGHDuplicate/conflicting requirement, untestable criterion
MEDIUMTerminology drift, missing NFR coverage
LOWStyle/wording, minor redundancy

Report Format

## Specification Analysis Report

| ID | Category | Severity | Location(s) | Summary | Recommendation |
|----|----------|----------|-------------|---------|----------------|
| A1 | Duplication | HIGH | spec.md:L120 | Similar requirements | Merge phrasing |

**Coverage Summary:**
| Requirement | Has Task? | Task IDs |
|-------------|-----------|----------|

**Metrics:**
- Total Requirements: X
- Coverage %: Y%
- Critical Issues: Z

Operating Constraints

  • STRICTLY READ-ONLY - No file modifications
  • Constitution is non-negotiable - Violations are CRITICAL
  • Max 50 findings (aggregate overflow)
  • Deterministic results on rerun

Next Actions

  • CRITICAL issues → Resolve before /spec-implement
  • LOW/MEDIUM only → May proceed with suggestions

Next Steps

After /spec-analyze:

  • Fix identified issues
  • /spec-implement - Execute implementation

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Research

research-engineer

No summary provided by upstream source.

Repository SourceNeeds Review
Research

wireshark network traffic analysis

No summary provided by upstream source.

Repository SourceNeeds Review
Research

content-research-writer

No summary provided by upstream source.

Repository SourceNeeds Review