kiro-validate-design

Review design.md, requirements.md, and spec.json for implementation readiness.

3.6k|274|Updated Jul 17, 2025
One-click install
npx skills add https://github.com/gotalab/cc-sdd --skill kiro-validate-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-validate-design
Source: https://github.com/gotalab/cc-sdd/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-validate-design
Command: npx skills add https://github.com/gotalab/cc-sdd --skill kiro-validate-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides an interactive, focused technical design review that detects critical issues and determines whether a design is ready for implementation, reducing costly rework and integration failures.

Core Features & Use Cases

  • Focused Critical Issue Detection: Identifies up to three highest-priority concerns that would block or impair implementation.
  • Balanced GO/NO-GO Decisioning: Produces a clear pass/fail decision with rationale and prioritized, actionable remediation steps.
  • Interactive Clarification: Engages the user with targeted questions and proposes alternative approaches when necessary.
  • Use Case: Validate a feature's design.md, requirements.md, and spec.json before generating tasks or starting implementation to avoid boundary violations and unmet constraints.

Quick Start

Run the kiro-validate-design skill for the feature payment to get a concise GO/NO-GO decision with up to three critical issues and suggested fixes.

Frequently Asked Questions about kiro-validate-design

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

FAQPage Schema
How do I validate a design spec before implementation?

Validate a design spec by running an interactive technical review on your design.md, requirements.md, and spec.json files to identify critical issues and produce a GO/NO-GO decision. This ensures implementation readiness and reduces rework.

What is a go-no-go design review for feature specifications?

A go-no-go design review assesses implementation readiness by identifying up to three critical issues in your feature specifications and providing a balanced pass/fail rationale with actionable remediation steps before task generation.

How do I check if my requirements.md and spec.json are ready for task generation?

Check implementation readiness by applying interactive spec validation to your requirements.md and spec.json files. The review identifies boundary violations and unmet constraints, then outputs a GO/NO-GO rationale with prioritized next steps.

Can I get interactive feedback on my architecture design to find blocking issues?

Yes, interactive design reviews engage you with targeted questions and propose alternative approaches when necessary. The process detects up to three highest-priority concerns that would block or impair implementation while respecting steering context.

When do I need a spec validation review for my software project?

You need a spec validation review in spec-driven projects to validate design.md, requirements.md, and spec.json files before task generation or implementation. It prevents costly rework by catching boundary violations and unmet constraints early.

Does the design validation respect existing steering context and language settings?

Yes, the design validation review respects your steering context and language settings while conducting the technical quality assessment. It provides prioritized, actionable remediation steps aligned with your project's established constraints.