بنقرة واحدة
design-review
Use when a design doc has been written and before draft-plan is dispatched
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when a design doc has been written and before draft-plan is dispatched
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants to view, change, or reset their persistent preferences, or when triggered by "/caliper-settings", "my settings", "change defaults".
Use when asked to audit a codebase, find DRY/YAGNI/complexity issues repo-wide, or perform periodic code quality review
Use when creating features, building components, adding functionality, or modifying behavior - before any creative or implementation work begins
Use when you have a spec or requirements for a multi-step task, before touching code
Use when implementing a small or medium change directly in the current session, without a multi-task plan — via design's fast-path routing, or direct invocation ("/implement", "just implement this", "quick fix").
Use when a multi-task implementation is complete and ready for holistic review before merging, or asked to review the current branch/diff as a whole
| name | design-review |
| description | Use when a design doc has been written and before draft-plan is dispatched |
Dispatch a reviewer subagent to validate a design doc before planning. Catches spec gaps that are cheap to fix in design but expensive to fix mid-implementation.
Core principle: Designs are hypotheses about what to build. Validate before committing to a plan.
Skip for: Trivially small changes with no design doc.
Gather inputs:
$MAIN_ROOT/.claude/claude-caliper/YYYY-MM-DD-topic/design-topic.md (main repo, not worktree)Dispatch with model: "$DESIGN_REVIEWER_MODEL" — review requires strong reasoning to catch blind spots the designer and user converged past.
Use subagent_type: "claude-caliper:design-reviewer". See: reviewer-prompt.md for invocation template.
Reviewer produces:
Pass: Zero issues, or all issues fixed and confirmed clean Fail: Return to design skill to fix, then re-run design-review
Review loop (two-pass cap): The design skill controls the loop: pass 1 is discovery. The lead fixes all findings and verifies each fix inline (grep/read). A delta pass 2 is dispatched only if pass 1 found critical or high issues; after pass 2, any remaining findings are fixed inline and the loop records pass — never a third dispatch. Delta dispatches receive the prior pass's issues with resolution status, enabling verify-then-scan instead of full re-discovery.
Note: Plan-review runs the same two-pass cap.
Auto-dispatched by: design (after design doc written)
Leads to: draft-plan (once review passes)