cc-requirement-gate

Analyze design specs to quantify requirement clarity and flag gaps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/z23cc/cc-code --skill cc-requirement-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-requirement-gate
Source: https://github.com/z23cc/cc-code/tree/main/skills/cc-requirement-gate
Command: npx skills add https://github.com/z23cc/cc-code --skill cc-requirement-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate requirements before planning — assess complexity, clarity, risks, and missing info. Prevents vague specs from entering implementation.

Core Features & Use Cases

  • Structured quality checks across Clarity, Completeness, Complexity, Feasibility, and Testability.
  • Gap discovery and risk identification with recommended questions.
  • Routing guidance to downstream workflows like cc-prd or cc-plan based on assessment outcomes.

Quick Start

Provide the design spec to the workflow and run the assessment to surface gaps and risks.

Frequently Asked Questions about cc-requirement-gate

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

FAQPage Schema
How do I validate requirements before planning to avoid ambiguity in design specs?

To validate requirements before planning, you can apply a structured rubric to design specs to identify gaps, quantify clarity, and flag risks. This prevents vague specs from entering implementation by producing a formal assessment report.

What is the best way to assess requirement clarity and feasibility for a new project?

The best way to assess requirement clarity is to run structured quality checks across Clarity, Completeness, Complexity, Feasibility, and Testability. This process surfaces missing info and identifies risks before development begins.

How do I identify gaps and risks in design specs from brainstorming sessions?

You can identify gaps and risks in brainstorming outputs by applying an assessment workflow to the design specs. It analyzes the inputs to discover missing information and outputs recommended questions to resolve ambiguities.

Can I route my design spec to a PRD or planning stage after requirement assessment?

Yes, you can route design specs to PRD or plan stages based on assessment outcomes. The evaluation produces routing guidance to direct downstream workflows, ensuring only validated requirements move forward.

Do I need any specific dependencies to run requirement checks on my design specs?

No specific dependencies are required to run requirement checks on design specs. You simply provide the spec inputs from your brainstorming sessions and run the assessment to surface gaps and risks.

When should I not use a structured requirement assessment workflow?

You should not use a structured requirement assessment if your design specs lack sufficient detail for evaluation, as the rubric requires baseline spec inputs to effectively identify gaps, quantify clarity, and flag risks.