speckit-analyze

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

1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ahmed8mansour/LMS --skill speckit-analyze-ahmed8mansour
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/ahmed8mansour/LMS/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/ahmed8mansour/LMS --skill speckit-analyze-ahmed8mansour

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies inconsistencies, missing coverage, ambiguity, and quality issues across project specification artifacts before implementation, helping teams catch planning problems early.

Core Features & Use Cases

  • Cross-Artifact Analysis: Reviews spec.md, plan.md, and tasks.md together to detect duplication, conflicts, missing requirements, and unclear definitions.
  • Coverage Validation: Maps requirements and success criteria to implementation tasks while identifying unmapped work and gaps.
  • Use Case: A development team can run this Skill after task generation to receive a structured quality report before coding begins.

Quick Start

Use the speckit-analyze skill to review my generated specification, plan, and tasks for inconsistencies and missing coverage.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
How do I check spec.md, plan.md, and tasks.md for inconsistencies before coding?

To check spec.md, plan.md, and tasks.md for inconsistencies, you can analyze project planning artifacts to identify duplication, conflicts, and missing requirements across specifications and implementation tasks. This cross-artifact analysis detects quality issues early.

What is requirements coverage validation in software planning?

Requirements coverage validation in software planning is the process of mapping requirements and success criteria to implementation tasks to identify unmapped work and gaps. It ensures every specified requirement has traceable implementation tasks before development begins.

How do I validate generated tasks against a spec-kit structure?

You validate generated tasks against a spec-kit structure by running a read-only artifact inspection after task generation. This performs requirement mapping and coverage analysis to produce a structured quality report highlighting risks and recommendations before coding.

Can I use cross-artifact analysis for pre-implementation task validation?

Yes, you can use cross-artifact analysis for pre-implementation task validation. It reviews project specification artifacts together to detect unclear definitions, missing coverage, and quality issues, providing a structured report of risks and recommendations.

Does consistency checking modify my project artifacts during analysis?

Consistency checking does not modify your project artifacts during analysis. The process requires read-only artifact inspection to map requirements, analyze coverage, and report risks, ensuring your original specifications, plans, and tasks remain unchanged.