skills.rest
aboneto
abonetoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

speckit.analyze

Identify cross-artifact inconsistencies among spec.md, plan.md, and tasks.md.

Updated Apr 20, 2026
Search Tags:#consistency#quality#spec#tasks#plan#analyze#check
One-click install
npx skills add https://github.com/aboneto/sopelasobremesa --skill speckit-analyze-aboneto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit.analyze
Source: https://github.com/aboneto/sopelasobremesa/tree/main/.agents/skills/speckit.analyze
Command: npx skills add https://github.com/aboneto/sopelasobremesa --skill speckit-analyze-aboneto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams surface cross-artifact inconsistencies between spec.md, plan.md, and tasks.md after task generation, enabling faster remediation and alignment.

Core Features & Use Cases

  • Cross-artifact consistency checks across spec, plan, and tasks to surface mismatches.
  • Automated flagging of ambiguities and gaps to guide refinement before implementation.
  • Use Case: Before implementation, run this analysis to align artifacts and reduce rework.

Quick Start

Run the speckit.analyze command after your artifacts are generated to surface inconsistencies.

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 between spec, plan, and tasks files?▼

Cross-artifact consistency checks compare spec.md, plan.md, and tasks.md files to surface mismatches and gaps. This analysis operates within a spec-kit project structure using the .specify directory to locate and verify artifacts across multiple files.

Why do my spec.md and tasks.md files have conflicting requirements after generation?▼

Cross-artifact inconsistencies between spec.md, plan.md, and tasks.md often occur after task generation due to automated processing gaps. Running an analysis flags ambiguities and mismatches to guide refinement before implementation begins.

When should I run a cross-artifact consistency analysis in my workflow?▼

Run cross-artifact consistency checks before implementation to align spec, plan, and tasks artifacts. This reduces rework by surfacing mismatches and gaps early, enabling faster remediation when project artifacts are already generated.

Can I use this analysis without a .specify directory in my project?▼

No, the analysis operates within a spec-kit project structure and requires a .specify directory to locate and verify artifacts across multiple files. This directory setup is necessary to perform cross-artifact consistency checks between spec.md, plan.md, and tasks.md.

What is the best way to find gaps between a project plan and its task list?▼

Automated cross-artifact consistency checking is the best way to find gaps between plan.md and tasks.md. It produces actionable findings with structured outputs suitable for remediation planning and extension hooks after generation.

What limitations exist when checking cross-artifact consistency in spec-kit projects?▼

Cross-artifact consistency checks are limited to spec.md, plan.md, and tasks.md files within a spec-kit project structure. The analysis requires a .specify directory and focuses on flagging ambiguities and gaps rather than automatically fixing them.

Related Skills

Explore More Software Engineering Skills→
PieroSierraPieroSierra
128

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for consistency and quality.

Community
Advanced
auleewilliamsauleewilliams

speckit-analyze

Detect inconsistencies across spec.md, plan.md, and tasks.md files.

Community
Advanced
vineethsomavineethsoma

spec-driven-development

Create and refine feature specifications before coding using the GitHub spec-kit workflow.

Community
Advanced
xiayipingxiayiping

千万级数据对账

Identifies matches and discrepancies between two massive datasets using scalable techniques like Spark or hashing-based matching.

Community
Advanced