One-click install
npx skills add https://github.com/StrangeDaysTech/arborist-cli --skill speckit-analyze-strangedaystech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-analyze
Source: https://github.com/StrangeDaysTech/arborist-cli/tree/main/.claude/skills/speckit-analyze
Command: npx skills add https://github.com/StrangeDaysTech/arborist-cli --skill speckit-analyze-strangedaystech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted engineering effort by detecting inconsistencies, duplicates, ambiguities, and missing coverage across your spec, plan, and generated tasks artifacts before implementation starts.

Core Features & Use Cases

  • Cross-artifact consistency analysis: Compares requirements and success criteria in spec.md against architecture choices and constraints in plan.md, and then checks whether tasks.md actually covers them.
  • Duplication and ambiguity detection: Flags near-duplicate requirements and vague or unmeasurable success criteria, plus unresolved placeholders.
  • Constitution-aligned validation: Ensures analysis adheres to the non-negotiable principles in .specify/memory/constitution.md, treating MUST conflicts as critical.
  • Read-only, report-only output: Produces a structured Markdown report without modifying files and recommends an optional remediation plan only after user approval.

Quick Start

Ask to run speckit-analyze after tasks generation to get a structured report of inconsistencies and coverage gaps across 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 spec-plan-task consistency before coding starts?

Spec-plan-task consistency is verified by cross-referencing requirements in spec.md, architectural constraints in plan.md, and generated tasks in tasks.md to detect duplication, ambiguity, and coverage gaps before implementation begins.

What is requirements traceability analysis for generated task lists?

Requirements traceability analysis checks whether generated tasks.md items actually cover the functional requirements and success criteria defined in spec.md, flagging any underspecified or missing coverage gaps in a structured report.

How do I detect duplication and ambiguity across specification and planning documents?

Duplication and ambiguity detection scans spec.md, plan.md, and tasks.md to flag near-duplicate requirements, vague success criteria, and unresolved placeholders, ensuring cross-artifact consistency and measurable project planning.

Can I enforce constitution compliance during specification analysis without modifying files?

Constitution compliance is enforced during specification analysis by validating artifacts against .specify/memory/constitution.md, treating MUST conflicts as critical while maintaining a strictly read-only validation that outputs a report without modifying files.

When do I need to run a consistency checking report on my project planning artifacts?

Consistency checking reports are needed immediately after tasks generation, ensuring the tasks.md file aligns with functional requirements and architectural constraints to prevent wasted engineering effort before implementation starts.

Does specification analysis work without a constitution.md file?

Specification analysis primarily targets cross-artifact consistency and coverage metrics between spec.md, plan.md, and tasks.md, while constitution conflicts from .specify/memory/constitution.md are treated as critical severity findings if that file exists.