ywc-spec-validate

Name: ywc-spec-validate
Availability: InStock
Author: yongwoon

Validate technical specification completeness, consistency, feasibility, and code compatibility.

8|1|Updated May 13, 2026

Search Tags:#planning #architecture #quality assurance #specification #validation #review

Ready to run

npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-spec-validate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ywc-spec-validate
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-spec-validate
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-spec-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes references (resource) components.

What problem does it solve?

This skill prevents costly implementation rework by validating the completeness, consistency, feasibility, and code compatibility of your technical specifications before task decomposition begins.

Core Features & Use Cases

Multi-Dimensional Review: Automatically checks specs against four critical dimensions: completeness, consistency, feasibility, and code compatibility.
Cross-Artifact Analysis: Verifies that generated tasks align perfectly with spec requirements, ensuring no orphaned tasks or uncovered requirements.
Use Case: Before starting a new backend API feature, run this skill to catch missing edge cases, terminology mismatches, or conflicts with existing database schemas.

Quick Start

Use the ywc-spec-validate skill to review the specification file located at docs/outline/02-backend-api-design.md.

Frequently Asked Questions about ywc-spec-validate

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

FAQPage Schema

How do I validate technical specification quality before implementation?▼

Validating technical specification quality requires analyzing completeness, consistency, feasibility, and code compatibility against project context. This process catches missing edge cases, terminology mismatches, and architectural conflicts before task decomposition begins.

What is cross-artifact consistency checking in specification review?▼

Cross-artifact consistency checking verifies that generated tasks align perfectly with specification requirements. This analysis detects orphaned tasks and uncovered requirements by comparing specification documents against planned implementation artifacts.

How do I check if a backend API design specification conflicts with existing database schemas?▼

Checking specification code compatibility involves analyzing the design document against existing database schemas and project context. This validation identifies terminology mismatches and architectural alignment issues before development starts.

Can I use parallel subagent analysis for specification validation?▼

Parallel subagent analysis enables multi-dimensional specification review by simultaneously checking completeness, consistency, feasibility, and code compatibility. This approach efficiently detects artifact drift and architectural misalignment.

Does the specification validation skill require gh to run?▼

Yes, the specification validation skill requires the gh dependency to execute. This command-line tool enables the skill to access repository context and perform project-level validation checks.

When should I run specification validation in the planning phase?▼

Run specification validation during the planning phase before task decomposition and implementation begin. This prevents costly rework by ensuring specifications are complete, feasible, and compatible with existing code.