speckit-analyze

Name: speckit-analyze
Availability: InStock
Author: Kami

Analyze Spec Kit artifacts for inconsistencies, duplications, ambiguities, and missing coverage.

Updated May 18, 2026

Search Tags:#consistency #requirements #analysis #constitution #spec kit #task coverage

Ready to run

npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-analyze-kamijeong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-analyze-kamijeong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review a Spec Kit project before implementation by finding inconsistencies, duplicates, ambiguities, missing coverage, and constitution conflicts across spec.md, plan.md, and tasks.md.

Core Features & Use Cases

Cross-artifact consistency analysis: Compares requirements, architecture choices, and task lists to spot drift or contradictions.
Coverage validation: Identifies requirements or success criteria that do not have supporting tasks, and tasks that do not map back to the spec.
Quality and alignment checks: Flags vague language, underspecified items, and violations of the project constitution so they can be fixed early.
Use case: A project team uses this Skill after task generation to confirm that every required feature is covered and that no task conflicts with the approved constitution.

Quick Start

Ask for a read-only analysis of the current Spec Kit artifacts and request the top inconsistencies, coverage gaps, and constitution issues.

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 consistency before implementation using Spec Kit?▼

To check spec consistency, analyze Spec Kit artifacts including spec.md, plan.md, and tasks.md to identify inconsistencies, duplications, and ambiguities before implementation begins.

What is task-to-requirement mapping in project specification analysis?▼

Task-to-requirement mapping validates coverage by identifying requirements lacking supporting tasks and flagging tasks that do not map back to the original specification document.

How do I validate constitution compliance in a Spec Kit project?▼

Validate constitution compliance by checking spec.md, plan.md, and tasks.md against project rules to detect and report violations, ensuring no task conflicts with the approved constitution.

Does Spec Kit analysis work with projects using a .specify directory?▼

Yes, Spec Kit analysis applies to projects using a .specify directory and a task generation workflow, reading the existing artifacts to perform a read-only review of gaps and conflicts.

What is the best way to find unimplemented requirements in task generation?▼

The best way to find unimplemented requirements is performing a coverage validation across your spec and task lists to identify required features or success criteria lacking supporting tasks.

Why does cross-artifact consistency analysis flag vague language in specs?▼

Cross-artifact consistency analysis flags vague language and underspecified items to catch quality and alignment issues early, preventing ambiguity from causing drift or contradictions during implementation.