speckit-analyze

Analyzes spec.md, plan.md, and tasks.md for cross-artifact consistency and coverage gaps.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-analyze-omkar-code-mur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/Omkar-code-mur/Job-Radar/tree/main/Spec-it_job-Radar/.github/skills/speckit-analyze
Command: npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-analyze-omkar-code-mur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent or incomplete specifications cause implementation failures. This Skill performs a read-only cross-artifact analysis across spec.md, plan.md, and tasks.md in a spec-kit project, detecting duplications, ambiguities, underspecification, constitution violations, and coverage gaps before coding begins. ## Core Features & Use Cases - Cross-Artifact Consistency Checks: Detects terminology drift, conflicting requirements, and data entities referenced in one artifact but missing from others. - Coverage Mapping: Maps every functional requirement and success criterion to tasks, flagging requirements with zero task coverage and unmapped tasks. - Severity-Ranked Report: Produces a structured Markdown report with CRITICAL/HIGH/MEDIUM/LOW findings, coverage tables, and metrics, capped at 50 findings. - Use Case: After running /speckit-tasks, invoke this analysis to verify that all requirements have task coverage and no constitution violations exist before starting implementation. ## Quick Start Ask the assistant to run the speckit-analyze skill to check consistency and coverage across the current feature's spec, plan, and tasks files.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
How do I check consistency between spec, plan, and tasks files?

Run the speckit-analyze skill after generating tasks.md. It loads spec.md, plan.md, and tasks.md, builds requirement and task inventories, and reports duplications, ambiguities, inconsistencies, and coverage gaps in a severity-ranked table.

When should I run spec-kit analysis in the workflow?

Run it after /speckit-tasks has produced a complete tasks.md and before /speckit-implement. The analysis aborts with an error if tasks.md is missing, since coverage mapping requires all three artifacts.

Does the analysis modify my specification files?

No, the analysis is strictly read-only. It outputs a structured Markdown report and optionally suggests remediation edits, but it never modifies spec.md, plan.md, tasks.md, or any other file.

What counts as a critical issue in spec analysis?

Critical issues include violations of constitution MUST principles, missing core spec artifacts, and requirements with zero task coverage that block baseline functionality. Constitution conflicts are always CRITICAL and cannot be downgraded.

Why does the analysis report zero findings?

A zero-finding report means no duplications, ambiguities, inconsistencies, or coverage gaps were detected across the three artifacts. The report still includes coverage statistics confirming requirements map to tasks.