skills.rest
j5ik2o
j5ik2oCOMMUNITY
Explore all skills by this author →
Website𝕏@j5ik2oGitHub

kiro-validate-design

Reviews technical design documents against requirements and architecture to produce GO/NO-GO decisions.

Updated Jun 23, 2026
Search Tags:#architecture#spec-driven#requirements#validation#technical design#design review#go no-go
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-validate-design-j5ik2o
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-validate-design
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/kiro-validate-design
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-validate-design-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It catches critical flaws in technical design documents before implementation begins, preventing costly rework by validating designs against requirements, existing architecture, and project standards. ## Core Features & Use Cases - Interactive Design Review: Analyzes design documents against requirements, steering context, and codebase patterns, then engages in dialogue with clarifying questions and alternatives. - Structured GO/NO-GO Assessment: Produces a balanced review with at most 3 critical issues (with impact, recommendation, traceability, and evidence), 1-2 strengths, and a clear decision with next steps. - Use Case: After generating a design document for a new feature, run this review to verify architecture alignment, type safety, and extensibility before generating implementation tasks. ## Quick Start Ask the assistant to validate the design for your feature, for example: run kiro-validate-design on my user-authentication feature to check if the design is ready for implementation.

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 technical design document before implementation?▼

Run the design validation review after generating your design document. It reads requirements.md, design.md, and steering context, then produces critical issues, strengths, and a GO/NO-GO decision with next steps.

What criteria are used in a design quality review?▼

The review evaluates existing architecture alignment, design consistency and standards, extensibility and maintainability, and type safety and interface design. Only issues significantly impacting success are flagged, limited to three.

What happens if the design document does not exist?▼

The review stops with a message instructing you to run the design generation step first. If the design phase is not marked as generated in spec.json, it warns but still proceeds with the review.

What should I do after a GO or NO-GO design decision?▼

On a GO decision, generate implementation tasks with the task generation command. On a NO-GO decision, address the critical issues, regenerate the design, and re-run the validation review.

Does the design review support languages other than English?▼

Yes, output language is read from the spec.json file for the feature. If no language is specified there, the review defaults to English.

Related Skills

Explore More Software Engineering Skills→
gotalabgotalab
3.6k

kiro-spec-status

Parse Kiro spec files to compute phase progress and task counts.

Community
Intermediate
DraculaboDraculabo
2.1k

openspec-apply-change

Implements tasks from an OpenSpec change using the openspec CLI.

Community
Intermediate
AutoByteusAutoByteus
2

architecture-reviewer

Review software design packages and route findings to the correct owner before implementation.

Official
Advanced
mikalvmikalv

grill-with-docs

Runs a structured design interview that produces ADRs and a glossary.

Community
Basic