cw-validate

Validate implemented specs against gates and proof artifacts in Claude Workflow projects.

14|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/sighup/claude-workflow --skill cw-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cw-validate
Source: https://github.com/sighup/claude-workflow/tree/main/skills/cw-validate
Command: npx skills add https://github.com/sighup/claude-workflow --skill cw-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates completed specifications by systematically verifying proof artifacts, coverage, and credential safety through a structured 6-gate process, ensuring implementation integrity.

Core Features & Use Cases

  • Performs cross-checks of functional requirements against tasks and associated proofs.
  • Generates a comprehensive coverage matrix and a formal validation report for traceability.
  • Re-executes automated proofs where possible to confirm results remain valid and flags credential risks.

Quick Start

Run the cw-validate workflow on your current feature branch to produce a validation report.

Frequently Asked Questions about cw-validate

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

FAQPage Schema
How do I validate implemented specs against functional requirements?

Spec validation cross-checks functional requirements against tasks and proofs, enforcing traceability and generating a coverage matrix. It systematically verifies implementation integrity through a 6-gate process to confirm all criteria are met.

What is the best way to automate proof artifact verification for feature branches?

Automated proof artifact verification re-executes proofs on your feature branch to confirm results remain valid. It systematically checks coverage and flags credential risks across tasks and commits without manual intervention.

How does credential safety checking work during spec validation?

Credential safety checking scans proof artifacts during validation to identify and flag potential credential risks. It operates as one of six gates, ensuring sensitive data exposure is detected before merging validated specifications.

Can I generate a traceability report for functional requirement coverage?

A traceability report is generated automatically by producing a comprehensive coverage matrix. This matrix maps functional requirements to tasks and proofs, providing formal validation documentation for completed implementations.

Do I need Claude Workflow projects to use the 6-gate validation process?

The 6-gate validation process applies specifically to Claude Workflow projects to verify proofs, coverage, and credential safety. It requires implemented specs and defined gates to execute end-to-end validation across tasks and commits.

Why does spec validation fail when proof artifacts are missing?

Spec validation fails because the 6-gate process requires proof artifacts to verify functional requirement traceability and re-execute automated proofs. Missing artifacts prevent comprehensive coverage matrix generation and halt the validation report output.