spec-consistency-analysis

Detect gaps and conflicts across specifications, plans, tasks, and write-sets before execution.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill spec-consistency-analysis-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-consistency-analysis
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/spec-consistency-analysis
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill spec-consistency-analysis-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Before implementation begins, specifications, architecture plans, and task decompositions often drift apart, causing requirements without tasks, tasks without write-sets, or plans that contradict approved specs. This Skill performs a read-only cross-artifact analysis to surface those inconsistencies while changes are still cheap. ## Core Features & Use Cases - Cross-artifact consistency checks: Runs ten defined checks covering missing acceptance criteria, orphaned requirements, stale references, write-set gaps, and scope contradictions. - Deterministic traceability support: Invokes scripts/validate-define-traceability.py as structural evidence when the stable-ID format is in use, while performing semantic checks separately. - Strict read-only boundary with routed remediation: Never mutates artifacts; each finding is routed to the owning artifact (specification, architecture, task decomposition, or Work Block) with a final verdict of READY, CHANGES_REQUIRED, BLOCKED, or UNVERIFIED. - Use Case: Before starting an Execute phase, run the analysis against the approved spec, accepted plan, and active tasklist to confirm every requirement has a measurable acceptance criterion, an implementation task, and an explicit write-set. ## Quick Start Analyze the approved specification, architecture plan, and current tasklist for consistency issues and report a findings matrix with a final verdict.

Frequently Asked Questions about spec-consistency-analysis

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

FAQPage Schema
How do I check specification consistency before implementation?▼

Run a pre-execution consistency analysis comparing the approved specification against the accepted architecture plan and task decomposition. It checks for requirements without acceptance criteria or tasks, stale references, and write-set gaps, then returns a findings matrix with a verdict.

What does a requirements traceability check cover?▼

It verifies every approved requirement has a measurable acceptance criterion and an implementation task, that references are not stale, and that each requirement task has an explicit write-set. A deterministic script validates stable-ID traceability structure while semantic checks run separately.

Does the consistency analysis modify my specification or plan files?▼

No, the analysis is strictly read-only for normative artifacts. It reports inconsistencies and routes remediation to the owner of each broken artifact, such as specification revision for requirements gaps or plan revision for architecture contradictions.

What do the READY, CHANGES_REQUIRED, BLOCKED, and UNVERIFIED verdicts mean?▼

READY means no unresolved material inconsistency exists. CHANGES_REQUIRED means owning artifacts need correction, BLOCKED means required decisions or evidence are unavailable, and UNVERIFIED means artifacts could not be inspected reliably.

Does a READY result grant permission to write source code?▼

No, a READY consistency result is only pre-execution evidence. It does not grant source write authority and does not replace the separate Critic review gate in the governance workflow.