design-review

When this skill is invoked:

1. Read the target design document in full.

1. Read the master CLAUDE.md to understand project context and standards.

1. Read related design documents referenced or implied by the target doc

(check design/docs/ for related systems).

1. Evaluate against the Design Document Standard checklist:
2. [ ] Has Overview section (one-paragraph summary)
3. [ ] Has User Fantasy section (intended feeling)
4. [ ] Has Detailed Rules section (unambiguous mechanics)
5. [ ] Has Formulas section (all math defined with variables)
6. [ ] Has Edge Cases section (unusual situations handled)
7. [ ] Has Dependencies section (other systems listed)
8. [ ] Has Tuning Knobs section (configurable values identified)
9. [ ] Has Acceptance Criteria section (testable success conditions)

1. Check for internal consistency:
2. Do the formulas produce values that match the described behavior?
3. Do edge cases contradict the main rules?
4. Are dependencies bidirectional (does the other system know about this one)?

1. Check for implementability:
2. Are the rules precise enough for a programmer to implement without guessing?
3. Are there any "hand-wave" sections where details are missing?
4. Are performance implications considered?

1. Check for cross-system consistency:
2. Does this conflict with any existing mechanic?
3. Does this create unintended interactions with other systems?
4. Is this consistent with the product's established tone and pillars?

1. Output the review in this format:

## Design Review: [Document Title]

### Completeness: [X/8 sections present]
[List missing sections]

### Consistency Issues
[List any internal or cross-system contradictions]

### Implementability Concerns
[List any vague or unimplementable sections]

### Balance Concerns
[List any obvious balance risks]

### Recommendations
[Prioritized list of improvements]

### Verdict: [APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED]

1. Contextual next step recommendations:
2. If the document being reviewed is product-concept.md or product-pillars.md:
3. Check if design/docs/systems-index.md exists
4. If it does NOT exist, add to Recommendations:

> "This concept is ready for systems decomposition. Run /map-systems > to break it down into individual systems with dependencies and priorities, > then write per-system PRDs."

• If the document is an individual system PRD:
• Check if the systems index references this system
• If verdict is APPROVED: suggest "Update the systems index status for

this system to 'Approved'."

• If verdict is NEEDS REVISION or MAJOR REVISION NEEDED: suggest "Update

the systems index status for this system to 'In Review'."

• Note: This skill is read-only. The user (or /design-system) must

perform the actual status update in the systems index.

Protocol

• Question: Auto-starts from argument (path to design doc)
• Options: Skip — single review path
• Decision: Skip — verdict is advisory
• Draft: Full review shown in conversation only
• Approval: Skip — read-only; this skill never writes files

Output

Deliver exactly:

• Completeness score (X/8 required sections present)
• Consistency issues — contradictions or undefined terms (or "None")
• Implementability concerns — sections too vague to build from (or "None")
• Verdict: APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED
• Next skill — one recommended follow-up (e.g., /map-systems, update systems index)