speckit-analyze

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

Updated Mar 29, 2026

Search Tags:#consistency #requirements #constitution #quality #traceability #analyze #artifact-review

Ready to run

npx skills add https://github.com/iltan987/jetadisyon --skill speckit-analyze-iltan987

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/iltan987/jetadisyon/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/iltan987/jetadisyon --skill speckit-analyze-iltan987

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perform cross-artifact analysis to identify inconsistencies and quality gaps across spec.md, plan.md, and tasks.md after task generation, enabling early remediation before implementation.

Core Features & Use Cases

Detect cross-artifact inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md.
Surface actionable remediation guidance and traceability gaps to satisfy constitution constraints.
Support pre-activation reviews by providing a compact, structured analysis ready for follow-up edits.

Quick Start

Run the speckit-analyze command after tasks.md is generated to produce a findings report.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema

How do I check for cross-artifact inconsistencies between spec.md, plan.md, and tasks.md?▼

Cross-artifact inconsistencies across spec.md, plan.md, and tasks.md are identified by analyzing traceability, flagging coverage gaps, and validating architecture decisions against functional requirements before implementation begins.

When do I need to analyze spec-kit artifacts for requirements traceability?▼

Requirements traceability analysis is needed during pre-implementation review after tasks.md is generated, ensuring functional requirements, architecture decisions, and task coverage align with constitution constraints before coding starts.

What is the best way to validate task coverage against functional requirements before implementation?▼

The best way to validate task coverage is running a cross-artifact analysis after task generation to surface underspecified items, duplications, and ambiguities across spec.md, plan.md, and tasks.md for early remediation.

Does spec-kit cross-artifact analysis detect ambiguities and duplications in generated tasks?▼

Yes, cross-artifact analysis detects ambiguities, duplications, and underspecified items across spec.md, plan.md, and tasks.md, providing actionable remediation guidance to satisfy constitution constraints during pre-activation reviews.

How do I ensure constitution rules are satisfied during pre-activation review of spec-kit artifacts?▼

Constitution rules are satisfied by performing cross-artifact analysis that flags traceability gaps, validates functional requirements against architecture decisions, and surfaces structured findings ready for follow-up edits before implementation.

What are the limitations of analyzing spec-kit artifacts for quality gaps after task generation?▼

This analysis is limited to projects using the spec-kit structure, focusing on pre-implementation review of spec.md, plan.md, and tasks.md to identify inconsistencies and quality gaps without modifying the artifacts directly.