skills.rest
benjaminshoemaker
benjaminshoemakerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-verification

Verify specification documents for upstream fidelity and quality issues.

39|5|Updated Dec 28, 2025
Search Tags:#documentation#specifications#verification#quality#traceability#upstream
One-click install
npx skills add https://github.com/benjaminshoemaker/ai_coding_project_base --skill spec-verification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-verification
Source: https://github.com/benjaminshoemaker/ai_coding_project_base/tree/main/.claude/skills/spec-verification
Command: npx skills add https://github.com/benjaminshoemaker/ai_coding_project_base --skill spec-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill verifies generated specification documents to ensure upstream requirements are preserved and quality issues are detected.

Core Features & Use Cases

  • Upstream fidelity checks: Ensures downstream specs retain key requirements and constraints from upstream documents.
  • Quality anti-pattern detection: Flags vague language, missing rationale, and untestable criteria.
  • Workflow-driven verification: Provides inline issue presentation, user-guided resolutions, and automatic re-verification after fixes.

Quick Start

After generating specs, run the verification workflow to check TECHNICAL_SPEC.md, EXECUTION_PLAN.md, and related feature specifications.

Frequently Asked Questions about spec-verification

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

FAQPage Schema
How do I verify that my technical specifications retain upstream requirements?▼

You can verify upstream fidelity in technical specifications by running a workflow that checks downstream documents like TECHNICAL_SPEC.md and EXECUTION_PLAN.md to ensure key requirements and constraints are preserved.

What are common quality anti-patterns in software specification documents?▼

Common quality anti-patterns in software specification documents include vague language, missing rationale, and untestable criteria, which verification workflows flag to ensure downstream specs maintain quality standards.

How do I check my execution plan for missing rationale or untestable criteria?▼

To check your execution plan for missing rationale or untestable criteria, run a specification verification workflow that flags quality anti-patterns in EXECUTION_PLAN.md and presents inline issues with guided resolutions.

Can I use specification verification for both greenfield and feature workflows?▼

Yes, specification verification can be used for both greenfield and feature workflows, as it applies to TECHNICAL_SPEC.md, EXECUTION_PLAN.md, and feature specs to enforce context preservation across various development stages.

How do I fix quality issues after running specification verification?▼

To fix quality issues after running specification verification, follow the user-guided resolutions provided inline, apply the fixes to your specification documents, and the workflow will automatically re-verify the updated specs.

Related Skills

Explore More Software Engineering Skills→
benjaminshoemakerbenjaminshoemaker
39

feature-plan

Generate EXECUTION_PLAN.md and AGENTS_ADDITIONS.md from feature specs.

Community
Advanced
sbalagan22sbalagan22

writing-plans

Document end-to-end implementation plans from specs with files, tests, and validation steps.

Community
Advanced
dmulcaheydmulcahey

plan-fidelity-review

Verify draft FeatureForge plans against CEO-approved specs for requirement coverage and topology fidelity.

Community
Advanced
spences10spences10
59

content-linter

Lint markdown content for spelling, en-GB compliance, and writing quality.

Community
Intermediate