design-review

Review design documents and produce severity-graded issue lists with fix suggestions.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill design-review-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/HACK-WU/skills/tree/main/skills/design-review
Command: npx skills add https://github.com/HACK-WU/skills --skill design-review-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Design documents often ship with structural gaps, vague decisions, and cross-document inconsistencies that surface only during implementation. This Skill performs a structured review of an existing design document and outputs a severity-graded issue list (blocking / suspected blocking / warning / suggestion) with concrete fix suggestions, so defects are caught before coding begins. ## Core Features & Use Cases - Five-dimension review: Checks structural completeness, content quality, technical correctness, cross-document consistency, and user experience (both positive and negative paths) across single files or multi-document design sets. - Format-aware baselines: Recognizes design-craft formatted documents (parent/child doc conventions) for precise baseline checks, and falls back to general review rules for free-form documents. - Confidence-graded technical challenges: Each technical challenge carries a confidence level; medium-confidence items are downgraded to "suspected blocking" requiring human confirmation rather than counted as hard blockers. - Incremental re-review: Given a revised document plus the previous review report, verifies fixes, scans only changed sections, and inherits previously passed items. - Use Case: After drafting a multi-document technical design with design-craft, ask for a review to receive a report listing blocking issues like missing interface return types, inconsistent API signatures between parent and child docs, and unsubstantiated "already supported" claims. ## Quick Start Review the design document at docs/user-management_DESIGN.md and give me a severity-graded issue list with fix suggestions.

Frequently Asked Questions about design-review

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

FAQPage Schema
How do I review a technical design document for defects?

Provide the design document and ask for a design review. The Skill runs staged checks across structure, content quality, technical correctness, consistency, and user experience, then outputs issues graded as blocking, suspected blocking, warning, or suggestion with specific fix guidance.

What document formats does design review support?

It natively recognizes design-craft format (parent document plus child docs named <feature>_S<XX>_<name>_DESIGN.md) and applies precise baseline checks. Free-form markdown design documents are also supported using general review rules in a degraded mode.

Can I re-review only the changed parts of a revised design doc?

Yes. Provide the revised document together with the previous review report to trigger incremental re-review. It verifies whether prior issues are fixed, scans only revised sections, and inherits previously passed items without repeating them.

When should I not use design review?

Do not use it when no readable design document exists yet; generate the document first with a design authoring skill. It also does not cross-validate against actual repository code, so conclusions are based solely on the document content.

How are uncertain technical challenges handled in the review report?

Each technical challenge carries a confidence label. Medium-confidence items are downgraded to a separate "suspected blocking" section that requires human confirmation and does not count toward hard blockers, while low-confidence items become optional suggestions.