Slash Command1.3k repo starsupdated today

review-design

The `/review-design` command audits feature design documentation against completeness criteria including architecture diagrams, component responsibilities, technology rationale, data models, API contracts, and design trade-offs. Use it after requirements are finalized to validate that a feature design document sufficiently addresses all technical concerns before implementation planning, employing iterative questioning and brainstorming to resolve gaps and ambiguities.

View source Repository: ai-devkit

Install in Claude Code

Copy

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/codeaholicguy/ai-devkit/HEAD/commands/review-design.md -o ~/.claude/commands/review-design.md

Then start a new Claude Code session; the slash command loads automatically.

Definition

review-design.md

Review design using the latest matching `docs/ai/design/YYYY-MM-DD-feature-{name}.md`. If none exists, use `docs/ai/design/feature-{name}.md`. Check the project-level README if relevant.

1. **Use Memory for Context** — Search memory for prior architecture constraints/patterns: `npx ai-devkit@latest memory search --query "<feature design architecture>"`.
2. Summarize:
- Architecture overview (ensure mermaid diagram is present and accurate)
- Key components and their responsibilities
- Technology choices and rationale
- Data models and relationships
- API/interface contracts (inputs, outputs, auth)
- Major design decisions and trade-offs
- Non-functional requirements that must be preserved
3. **Clarify and explore (loop until converged)**:
- **Ask clarification questions** for every gap, inconsistency, or misalignment between requirements and design. Do not just list issues — actively ask specific questions to resolve them.
- **Brainstorm and explore options** — For key architecture decisions, trade-offs, or areas with multiple viable approaches, proactively brainstorm alternatives. Present options with pros/cons and trade-offs. Challenge assumptions and surface creative alternatives.
- **Repeat** — Continue looping until the user is satisfied with the chosen approach and no open questions remain.
4. **Store Reusable Knowledge** — Persist approved design patterns/constraints with `npx ai-devkit@latest memory store ...` when they will help future work.
5. **Next Command Guidance** — If requirements gaps are found, return to `/review-requirements`; if design is sound, continue to `/execute-plan`.