review-design

Validate DESIGN.md files against the SB design template.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill review-design-alo-exp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-design
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/review-design
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill review-design-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates DESIGN.md artifacts to ensure they meet the SB design template, enforcing completeness and consistency across design documentation.

Core Features & Use Cases

  • Automated validation of required sections (Screens, Components, Behavior Specifications, State Definitions) and detection of missing or empty fields.
  • Cross-reference capability with SPEC.md via the source_inputs pathway to identify orphaned components and traceability gaps.
  • Structured findings with PASS/ISSUES_FOUND results and DESIGN-F style issue codes for auditability.

Quick Start

Run the reviewer on a DESIGN.md file using either the artifact-reviewer interface or the /review-design command with an optional SPEC input path.

Frequently Asked Questions about review-design

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

FAQPage Schema
How do I validate a DESIGN.md file against the SB design template?

Validating a DESIGN.md file against the SB design template involves running an automated review that checks required sections like Screens, Components, Behavior Specifications, and State Definitions to detect missing or empty fields.

What is design QC criteria enforcement for design documents?

Design QC criteria enforcement for design documents is the automated process of checking frontmatter validity and required section completeness in DESIGN.md files, yielding structured PASS or ISSUES_FOUND results with DESIGN-F codes for auditability.

Can I cross-reference DESIGN.md with SPEC.md to find traceability gaps?

Yes, you can cross-reference DESIGN.md with SPEC.md by providing the SPEC input path, which identifies orphaned components and traceability gaps via the source_inputs pathway to ensure design alignment with specifications.

What are the required sections in an SB design template for a design review?

The required sections in an SB design template for a design review include Screens, Components, Behavior Specifications, and State Definitions, all of which must be present and non-empty to pass automated validation.

How do I get structured issue codes from a design document review?

You get structured issue codes from a design document review by running the validation process, which outputs DESIGN-F style codes and PASS or ISSUES_FOUND results to provide auditability for any detected completeness or consistency errors.

Does the design reviewer work without a SPEC.md file input?

Yes, the design reviewer works without a SPEC.md file by validating the DESIGN.md artifact independently, though providing the optional SPEC input path enables cross-referencing to detect orphaned components and traceability gaps.