skills.rest
kamalsroor1
kamalsroor1COMMUNITY
Explore all skills by this author →
GitHub

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and coverage gaps.

Updated Apr 10, 2026
Search Tags:#consistency#requirements#constitution#traceability#spec-kit#analyze#tasks-audit
One-click install
npx skills add https://github.com/kamalsroor1/nest-scaffolding-crud-manager --skill speckit-analyze-kamalsroor1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/kamalsroor1/nest-scaffolding-crud-manager/tree/main/.agent/skills/speckit-analyze
Command: npx skills add https://github.com/kamalsroor1/nest-scaffolding-crud-manager --skill speckit-analyze-kamalsroor1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a non-destructive, read-only audit of specification artifacts to detect inconsistencies, duplications, ambiguities, missing coverage, and constitution conflicts across spec.md, plan.md, and tasks.md so teams can remediate issues before implementation.

Core Features & Use Cases

  • Pre-execution Hook Detection: Reads .specify/extensions.yml and reports optional and mandatory pre- and post-analyze hooks without executing them.
  • Progressive Artifact Loading: Loads only necessary sections from SPEC, PLAN, TASKS and the constitution to minimize noise and tokens.
  • Semantic Modeling & Traceability: Builds requirements and user-story inventories, maps tasks to requirements, and extracts constitution rules to validate MUST/SHOULD constraints.
  • Detection Passes & Severity: Runs targeted checks for duplication, ambiguity, underspecification, coverage gaps, terminology drift, and ordering or technology conflicts and assigns CRITICAL/HIGH/MEDIUM/LOW severities.
  • Read-Only Remediation Guidance: Produces a compact Markdown report with a coverage summary, unmapped tasks, metrics, next actions, and an optional remediation suggestion prompt without modifying repository files.
  • Use Cases: Pre-implementation quality gate, specification audit before large refactors, or CI step to prevent shipping underspecified features.

Quick Start

Run the speckit-analyze skill against the feature directory produced by speckit.tasks to generate a structured specification analysis report.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
How do I audit cross-artifact consistency across spec.md, plan.md, and tasks.md?▼

Cross-artifact consistency auditing checks spec.md, plan.md, and tasks.md for inconsistencies, duplications, ambiguities, and coverage gaps. It builds a traceability model mapping tasks to requirements and outputs a structured Markdown report without modifying any files.

What is a pre-implementation specification audit and when do I need it?▼

A pre-implementation specification audit validates that requirements, plans, and tasks are fully aligned before coding begins. You need it as a quality gate before large refactors or as a CI step to prevent shipping underspecified features.

How do I check traceability between requirements and tasks in a spec-kit repository?▼

Checking traceability involves building a requirements and user-story inventory, then mapping tasks directly to requirements. This process identifies unmapped tasks and coverage gaps, assigning severity levels to any missing connections found.

Does the spec-kit audit execute pre-execution hooks during analysis?▼

No, the spec-kit audit reads .specify/extensions.yml to report optional and mandatory pre- and post-analyze hooks without executing them. This ensures the analysis remains completely read-only and non-destructive to your repository state.

Can I use this specification audit to enforce constitution MUST and SHOULD constraints?▼

Yes, you can enforce constitution constraints by extracting MUST and SHOULD rules during the semantic modeling phase. The audit validates these constraints against your artifacts and flags any conflicts with assigned severity levels in the final report.

What is the best way to detect terminology drift and underspecification in specification artifacts?▼

The best way to detect terminology drift and underspecification is running targeted detection passes that check for ordering conflicts, technology mismatches, and ambiguities. It assigns CRITICAL, HIGH, MEDIUM, or LOW severities to each detected issue.

Related Skills

Explore More Software Engineering Skills→
jineynejineyne

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for cross-artifact inconsistencies and coverage gaps.

Community
Advanced
XinheLIUXinheLIU

analyze

Compare spec.md, plan.md, and tasks.md to produce a read-only Markdown audit report.

Community
Advanced
dshearerdshearer
2

misatay-planning

Coordinate collaborative planning to decompose work into reviewable tasks with dependencies.

Community
Advanced
searchandrescueggsearchandrescuegg

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and coverage gaps.

Official
Intermediate