story-analyze

Analyze spec.md, plan.md, and tasks.md for consistency and generate analysis-report.md.

2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/telum-ai/speck --skill story-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-analyze
Source: https://github.com/telum-ai/speck/tree/main/.cursor/skills/story-analyze
Command: npx skills add https://github.com/telum-ai/speck --skill story-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies inconsistencies, duplications, ambiguities, and underspecified items across your project's core artifacts (spec.md, plan.md, tasks.md) before implementation begins, ensuring a high-quality and coherent development process.

Core Features & Use Cases

  • Cross-Artifact Analysis: Compares spec.md, plan.md, and tasks.md for consistency.
  • Quality Assurance: Detects vague language, missing details, and potential conflicts.
  • Constitution Compliance: Verifies adherence to project and epic principles.
  • Use Case: After generating tasks for a new feature, run this Skill to automatically generate a report highlighting any requirements that were missed in the task breakdown or any tasks that don't clearly map back to a specific requirement.

Quick Start

Run a thorough analysis of your current story's specifications, plan, and tasks to identify any inconsistencies or quality issues.

Frequently Asked Questions about story-analyze

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

FAQPage Schema
How do I check spec.md, plan.md, and tasks.md for consistency before implementation?

To check spec.md, plan.md, and tasks.md for consistency, you can run a cross-artifact analysis that detects duplications, ambiguities, and underspecified items across these files. This generates an analysis-report.md highlighting any inconsistencies in your project directory.

What is cross-artifact quality assurance for software specifications?

Cross-artifact quality assurance for software specifications is the process of comparing spec.md, plan.md, and tasks.md to identify vague language, missing details, and potential conflicts. It verifies that your task breakdown accurately maps back to your original requirements.

Do I need correctly formatted spec.md, plan.md, and tasks.md files to run an analysis?

Yes, you need correctly formatted spec.md, plan.md, and tasks.md files present in your story directory to run an analysis. The tool performs a non-destructive read of these required artifacts to generate the quality report.

What's the best way to find missing requirements in a task breakdown?

The best way to find missing requirements in a task breakdown is to perform an automated consistency check across your spec, plan, and tasks. This identifies any requirements missed during task generation and flags tasks lacking clear requirement mapping.

Why does my specification analysis report show constitution violations?

Your specification analysis report shows constitution violations because the tool verifies adherence to project and epic principles during its review. It flags any tasks or specifications that deviate from these established governing guidelines.