design-review
Skill for formal design review preparation and execution (PDR/CDR)
What this skill does
# Design Review Management Skill
## Purpose
The Design Review Management skill provides capabilities for preparing and executing formal design reviews (PDR/CDR), enabling systematic verification of design maturity and stakeholder alignment.
## Capabilities
- Design review agenda preparation
- Review criteria and checklist development
- Technical presentation guidance
- Action item tracking and management
- Review board coordination
- Design maturity assessment
- Gate criteria verification
- Review meeting facilitation
## Usage Guidelines
### Design Review Types
#### Review Gate Framework
| Review | Timing | Purpose | Key Questions |
|--------|--------|---------|---------------|
| SRR | Requirements phase | Requirements complete | Are requirements understood? |
| PDR | Preliminary design | Design approach approved | Will the design work? |
| CDR | Detailed design | Design ready for build | Is the design complete? |
| TRR | Test readiness | Ready for qualification | Can we test this? |
| PRR | Production | Ready for manufacturing | Can we build this? |
#### Preliminary Design Review (PDR)
```
Entry criteria:
- Requirements baselined
- Preliminary design complete
- Key trade studies completed
- Risk assessment performed
- Preliminary analysis complete
Exit criteria:
- Design approach approved
- Requirements verified feasible
- Major risks identified and mitigated
- Development plan approved
- Resources allocated
```
#### Critical Design Review (CDR)
```
Entry criteria:
- Detailed design complete
- All analysis complete
- Drawings released for review
- Bill of materials complete
- Manufacturing plan drafted
Exit criteria:
- Design frozen
- Analysis approved
- Drawings approved for release
- Manufacturing plan approved
- Test plan approved
```
### Review Preparation
#### Agenda Development
```
Standard review agenda:
1. Introduction and objectives (15 min)
2. Requirements review (30 min)
3. Design overview (45 min)
4. Analysis summary (30 min)
5. Manufacturing approach (30 min)
6. Test approach (30 min)
7. Risk assessment (30 min)
8. Schedule and cost (15 min)
9. Action items and closure (30 min)
```
#### Review Package
1. **Documentation**
- Design description
- Requirements verification matrix
- Analysis reports
- Drawings/models
- Risk register
- Development schedule
2. **Presentation Materials**
- Overview slides
- Technical deep-dive backup
- Supporting data
- Action item log (from previous review)
### Review Checklists
#### Design Checklist (Mechanical)
```
Requirements:
[ ] All requirements allocated and traceable
[ ] Derived requirements documented
[ ] Interface requirements defined
[ ] Verification methods assigned
Design:
[ ] Design meets all requirements
[ ] Design intent documented
[ ] Material selections justified
[ ] Tolerances appropriate for function
[ ] Accessibility for maintenance
[ ] Safety considerations addressed
Analysis:
[ ] Structural analysis complete
[ ] Thermal analysis complete
[ ] Fatigue life adequate
[ ] Weight budget met
[ ] Margins documented
Manufacturing:
[ ] Design is manufacturable
[ ] Tolerances achievable
[ ] Special processes identified
[ ] Supplier capability verified
[ ] Cost estimate complete
```
#### Risk Assessment Checklist
```
For each risk:
[ ] Risk clearly defined
[ ] Likelihood assessed
[ ] Consequence assessed
[ ] Mitigation plan defined
[ ] Responsible party assigned
[ ] Target closure date set
[ ] Status tracked
```
### Review Execution
#### Review Board Composition
| Role | Responsibility | Required/Optional |
|------|---------------|-------------------|
| Chair | Lead review, decisions | Required |
| Secretary | Record actions | Required |
| Chief Engineer | Technical authority | Required |
| Design Lead | Present design | Required |
| Analysis Lead | Present analysis | Required |
| Manufacturing | Assess producibility | Required |
| Quality | Compliance verification | Required |
| Customer | Requirements owner | Situational |
#### Decision Criteria
```
Review outcomes:
- APPROVED: All criteria met, proceed to next phase
- CONDITIONAL: Proceed with identified conditions
- NOT APPROVED: Return to previous phase
Voting process:
- Unanimous for approval
- Document dissenting opinions
- Escalation path for unresolved issues
```
### Action Item Management
#### Action Item Content
```
Required information:
- Unique ID
- Description
- Assigned to
- Due date
- Priority (high/medium/low)
- Status
- Closure criteria
- Resolution summary
```
#### Tracking Process
```
Action item lifecycle:
1. Opened at review
2. Assigned and acknowledged
3. Work in progress
4. Resolution proposed
5. Reviewed and verified
6. Closed
```
## Process Integration
- ME-024: Design Review Process (PDR/CDR)
## Input Schema
```json
{
"review_type": "SRR|PDR|CDR|TRR|PRR",
"project_info": {
"name": "string",
"phase": "string",
"schedule_date": "date"
},
"review_scope": {
"systems": "array",
"requirements": "array of requirement IDs"
},
"previous_actions": "array of action items",
"attendees": {
"required": "array",
"optional": "array"
}
}
```
## Output Schema
```json
{
"review_package": {
"agenda": "document reference",
"presentation": "file reference",
"checklists": "array of checklist references"
},
"review_results": {
"decision": "approved|conditional|not_approved",
"conditions": "array (if conditional)",
"action_items": [
{
"id": "string",
"description": "string",
"assigned_to": "string",
"due_date": "date",
"priority": "high|medium|low"
}
]
},
"maturity_assessment": {
"overall_score": "number (1-5)",
"by_area": "object",
"gaps_identified": "array"
},
"meeting_minutes": "document reference"
}
```
## Best Practices
1. Distribute review package in advance (1 week minimum)
2. Pre-brief key stakeholders on critical issues
3. Focus review time on decisions, not presentations
4. Document all action items with clear ownership
5. Follow up on action items before next review
6. Maintain consistent review standards across projects
## Integration Points
- Connects with Requirements Flowdown for verification
- Feeds into Change Management for design changes
- Supports Test Planning for verification evidence
- Integrates with Quality for compliance
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.