speckit-analyze

Analyze spec, plan, and task documents for consistency and alignment.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/fmbetancourt/famifinances --skill speckit-analyze-fmbetancourt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/fmbetancourt/famifinances/tree/main/.agents/skills/speckit-analyze
Command: npx skills add https://github.com/fmbetancourt/famifinances --skill speckit-analyze-fmbetancourt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill prevents implementation drift by identifying inconsistencies, ambiguities, and coverage gaps between your project's specification, planning, and task artifacts.

Core Features & Use Cases

  • Cross-Artifact Validation: Automatically checks spec.md, plan.md, and tasks.md for alignment and completeness.
  • Constitution Enforcement: Validates that all proposed work adheres to the project's non-negotiable principles defined in the constitution.
  • Use Case: Before starting a new feature implementation, run this skill to ensure your task list fully covers the success criteria defined in your spec and that no tasks violate project architecture rules.

Quick Start

Invoke the speckit-analyze skill to perform a full consistency check across your current feature artifacts.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
How do I check specification consistency across spec, plan, and task documents?

To check specification consistency, analyze cross-artifact alignment between spec.md, plan.md, and tasks.md to identify coverage gaps, ambiguities, and conflicts before implementation begins.

How do I prevent implementation drift in spec-driven development?

Prevent implementation drift by validating that your task list fully covers the success criteria defined in your spec and detecting potential conflicts across project artifacts prior to coding.

Do I need a .specify project structure to analyze task document alignment?

Yes, a valid .specify project structure is required to perform dependency and requirement mapping for cross-artifact consistency validation across your specification documents.

What is cross-artifact validation for project constitution enforcement?

Cross-artifact validation for constitution enforcement checks that all proposed work in your planning and task documents adheres to the non-negotiable architectural principles defined in your project.

When should I run a requirements coverage analysis for feature implementation?

Run requirements coverage analysis before starting a new feature implementation to ensure your tasks.md fully covers the success criteria defined in spec.md and no tasks violate project architecture rules.

Can I detect planning ambiguities and conflicts between specification documents?

Yes, you can detect planning ambiguities by evaluating requirement mapping and identifying potential conflicts between your specification, planning, and task artifacts to ensure alignment.