sdd-validate-design

Validate technical design documents and issue a GO/NO-GO decision.

Updated Dec 2, 2025
One-click install
npx skills add https://github.com/qlawmarq/dotfiles-common --skill sdd-validate-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-validate-design
Source: https://github.com/qlawmarq/dotfiles-common/tree/main/skills/sdd-init/references/skills/validate-design
Command: npx skills add https://github.com/qlawmarq/dotfiles-common --skill sdd-validate-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the technical design review process, ensuring designs are ready for implementation by providing a balanced assessment and a clear GO/NO-GO decision.

Core Features & Use Cases

  • Interactive Quality Review: Engages users in a dialogue to assess design documents against requirements and best practices.
  • Balanced Feedback: Identifies both critical issues and design strengths.
  • GO/NO-GO Decision: Provides a clear decision with actionable rationale and next steps.
  • Use Case: A developer has completed a design document for a new user authentication feature. They run this skill to get a quick, expert review before starting implementation, ensuring all requirements are met and potential blockers are identified.

Quick Start

Run the sdd-validate-design skill with the feature name 'user-authentication'.

Frequently Asked Questions about sdd-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?

To validate a technical design document, this Skill engages you in an interactive quality review process that assesses requirements and project context, ultimately delivering a GO/NO-GO decision and actionable feedback.

What is a go/no-go decision in software development design review?

A go/no-go decision in software development design review is a clear readiness assessment that determines if technical specifications meet requirements, accompanied by actionable rationale and next steps for implementation.

Can I get balanced feedback on both strengths and critical issues in my design?

Yes, you can get balanced feedback that identifies both critical issues and design strengths. The interactive review process highlights potential implementation blockers while acknowledging what works well in your technical specifications.

How do I assess implementation readiness for a new software feature?

You assess implementation readiness by running an interactive validation against requirements and best practices. The review analyzes your design specifications and project steering context to determine if the feature is ready for development.

Does the technical validation process require specific dependencies or components?

No, the technical validation process requires no external dependencies. It operates using a references component to guide the interactive quality review and assess your design document against project requirements.

When should I use an automated design review instead of manual evaluation?

You should use an automated design review when you need a quick, expert assessment of a completed design document before starting implementation, ensuring all requirements are met and potential blockers are identified efficiently.