cdd-review-decision

Name: cdd-review-decision
Availability: InStock
Author: yutaro

Validate DECIDED design decisions for alignment with architecture and related documents before implementation.

Updated Jan 21, 2026

Search Tags:#architecture #documentation #quality-assurance #cdd #design-review #context-gathering #decision-validation

Ready to run

npx skills add https://github.com/yutaro0915/cdd-workflow --skill cdd-review-decision

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cdd-review-decision
Source: https://github.com/yutaro0915/cdd-workflow/tree/main/src/templates/skills/cdd-review-decision
Command: npx skills add https://github.com/yutaro0915/cdd-workflow --skill cdd-review-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured design review to validate decisions labeled DECIDED before moving to implementation, ensuring architectural alignment and avoiding rework.

Core Features & Use Cases

Load and verify the decision document for consistency with architecture guidelines and related decisions.
Identify gaps in the Context section (gathered_context) and propose needed references to ensure completeness.
Recommend decisions to APPROVE or REQUEST_REVISION based on assessment, and generate a formal review report.

Quick Start

Ask the AI to review a DECIDED decision ID and verify context, consistency, and architectural alignment before implementation.

Frequently Asked Questions about cdd-review-decision

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

FAQPage Schema

How do I validate architecture decisions before starting implementation?▼

A design review validates DECIDED architecture decisions by checking frontmatter validity, verifying gathered context, and assessing consistency with related documents to formally recommend approval or request revision before coding begins.

What does a design review check before approving decided architecture decisions?▼

A design review checks a DECIDED decision's frontmatter validity, verifies the gathered context section for completeness, and ensures consistency with related workflows to generate a formal review report recommending APPROVE or REQUEST_REVISION.

How do I check if my decision document has sufficient context for a design review?▼

To check context sufficiency for a design review, identify gaps in the decision document's gathered_context section and propose needed references to ensure completeness, verifying that frontmatter metadata is valid before the assessment.

Can I use a design review to ensure architectural alignment before coding?▼

Yes, you can use a design review to ensure architectural alignment by loading and verifying the decision document against architecture guidelines and related decisions, generating a formal review report to prevent implementation rework.

What are the limitations of validating decisions using a design review?▼

The limitation of validating decisions with a design review is that it only applies to decisions with a DECIDED status, requiring valid frontmatter including id, title, decisionStatus, and metadata, along with a populated gathered_context section to function correctly.