speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and ambiguities.

180|11|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/serverless-dna/tendril --skill speckit-analyze-serverless-dna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/serverless-dna/tendril/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/serverless-dna/tendril --skill speckit-analyze-serverless-dna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md to ensure a coherent, high-quality design before implementation.

Core Features & Use Cases

  • Cross-artifact consistency checks between spec.md, plan.md, and tasks.md.
  • Detection of ambiguities and missing acceptance criteria with suggested remediation hints.
  • Generation of a structured analysis report aligned with the project constitution that can inform remediation planning.

Quick Start

Run the speckit.analyze command at the repo root to generate a structured analysis report from spec.md, plan.md, and tasks.md.

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 inconsistencies across spec, plan, and tasks files?

To check for inconsistencies across spec, plan, and tasks files, run a cross-artifact quality analysis to identify duplications, ambiguities, and underspecified items before implementation. This generates a structured report aligned with your project's constitution for remediation planning.

What is cross-artifact quality analysis for spec-plan-tasks triads?

Cross-artifact quality analysis is a structured review process for spec-plan-tasks triads that detects inconsistencies, missing acceptance criteria, and ambiguities. It enforces normative rules using your project's constitution as the source of truth to ensure a coherent design before implementation.

How do I detect missing acceptance criteria and ambiguities in my spec?

Detect missing acceptance criteria and ambiguities by running an automated analysis across your spec.md, plan.md, and tasks.md. The process identifies underspecified items and provides suggested remediation hints to refine your project's design.

Can I enforce constitution-derived MUST principles during spec analysis?

You can enforce constitution-derived MUST principles during spec analysis by using your project's constitution file as the source of truth. The analysis checks your spec, plan, and tasks artifacts against these normative rules to ensure compliance before implementation begins.

Does spec quality analysis work without a constitution file?

Spec quality analysis is designed to use the project's constitution file as the source of truth for normative rules. Without this file, the analysis cannot enforce the constitution-derived MUST principles required to validate the spec-plan-tasks triad.

When do I need to run a cross-artifact consistency check on my project docs?

You need to run a cross-artifact consistency check when a project produces a spec-plan-tasks triad and requires a structured quality review before implementation. It ensures your documentation is coherent, unambiguous, and fully specified to prevent downstream development issues.