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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents costly implementation churn by checking that your generated task plan matches your specification and that all core artifacts are consistent, complete, and constitution-aligned.

Core Features & Use Cases

  • Cross-artifact consistency review: Compares spec.md, plan.md, and tasks.md to detect duplicated, ambiguous, or conflicting requirements.
  • Coverage and traceability checks: Verifies that requirements and success criteria that should be buildable have corresponding task coverage, and flags unmapped tasks.
  • Constitution authority validation: Ensures principles marked as non-negotiable are not contradicted, treating such conflicts as CRITICAL.

Quick Start

Run the speckit-analyze command after tasks generation to produce a structured analysis report of inconsistencies and coverage gaps.

Frequently Asked Questions about speckit-analyze

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

FAQPage Schema
How do I check requirements traceability between spec, plan, and tasks files?

Cross-artifact consistency analysis compares spec.md, plan.md, and tasks.md to detect duplicated, ambiguous, or conflicting requirements after task generation.

How do I validate constitution alignment for generated task plans?

Constitution alignment validation ensures principles marked as non-negotiable MUST rules are not contradicted by your generated tasks, treating any such conflicts as CRITICAL issues.

When do I need to run cross-artifact consistency checking for speckit projects?

Cross-artifact consistency checking is needed after tasks generation to detect duplicated, ambiguous, or conflicting requirements before implementation begins, preventing costly rework.

Can I analyze task ordering and phase groupings without modifying my markdown artifacts?

Yes, non-destructive analysis loads feature_dir artifacts and constitution rules in strict read-only mode to verify task ordering, terminology, and phase groupings without modifying the files.

Does spec analysis work with FR and SC identifier structures?

Spec analysis applies to projects following speckit structure using FR and SC identifiers, plan phases, and task IDs to verify ordering, terminology, and required coverage across artifacts.