design-review

Review architectural designs for soundness before code builds.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill design-review-aabdulghany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/design-review
Command: npx skills add https://github.com/AAbdulghany/fms --skill design-review-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review a technical design / migration AgDR / feature spec for architectural soundness BEFORE the Build phase. Invokes the Solution Architect agent (Tariq) — the non-code analog of /code-review.

Core Features & Use Cases

  • Primary reviewer Tariq reviews the design against the architecture review lens (NFRs, patterns, tech debt, AgDR linkage, risk, trade-offs, traceability, migration safety) and codifies findings.
  • Escalation to the Head of Engineering for enterprise, cross-project, or new-tech-stack concerns.
  • Conditional Security Auditor: if the design touches auth / crypto / secrets / user data, chain to /security-review for deeper evaluation.
  • Adheres to the activation protocol described in .claude/rules/role-triggers for isolated-work-class.

Quick Start

Run the /design-review command against your design artifact to initiate the architecture review.

Frequently Asked Questions about design-review

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

FAQPage Schema
How do I review an architectural design before starting the build phase?

An architectural design review evaluates your PRDs, migration AgDRs, and feature specs for soundness before coding begins. It verifies alignment with architecture patterns, NFRs, risk, trade-offs, and deployment safety to prevent structural flaws early.

When do I need a solution architect to review my migration AgDR?

You need a solution architect to review your migration AgDR when you want to verify risk, traceability, and deployment safety before building. It applies architectural lenses like tech debt and NFRs to ensure the migration design is structurally sound.

Can I trigger a security review for feature specs that touch authentication or secrets?

Yes, you can trigger a conditional security review for feature specs touching auth, crypto, or secrets. The design review automatically chains to a security auditor to evaluate user data and authentication risks when these sensitive areas are detected.

How does a pre-build design review handle enterprise or cross-project architectural concerns?

A pre-build design review handles enterprise and cross-project concerns by escalating them to the Head of Engineering. This ensures that introducing new tech stacks or impacting multiple projects receives higher-level architectural oversight.

What is the difference between a code review and a design review for PRDs?

A design review for PRDs is a non-code analog to code review, evaluating architecture and risk before the build phase rather than inspecting written code. It assesses feature specs and migration AgDRs against patterns and NFRs to ensure structural soundness prior to implementation.