library/specializations/domains/science/mechanical-engineering/skills/design-review/SKILL.md
Skill for formal design review preparation and execution (PDR/CDR)
npx skillsauth add a5c-ai/babysitter design-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
| 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? |
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
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
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)
Documentation
Presentation Materials
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
For each risk:
[ ] Risk clearly defined
[ ] Likelihood assessed
[ ] Consequence assessed
[ ] Mitigation plan defined
[ ] Responsible party assigned
[ ] Target closure date set
[ ] Status tracked
| 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 |
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
Required information:
- Unique ID
- Description
- Assigned to
- Due date
- Priority (high/medium/low)
- Status
- Closure criteria
- Resolution summary
Action item lifecycle:
1. Opened at review
2. Assigned and acknowledged
3. Work in progress
4. Resolution proposed
5. Reviewed and verified
6. Closed
{
"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"
}
}
{
"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"
}
development
Model documentation skill for generating model cards following Google's model card framework.
development
MLflow integration skill for experiment tracking, model registry, and artifact management. Enables LLMs to log experiments, compare runs, manage model lifecycle, and retrieve artifacts through the MLflow API.
data-ai
LIME-based local explanation skill for individual predictions across tabular, text, and image data.
devops
Kubeflow Pipelines skill for ML workflow orchestration, component management, and Kubernetes-native ML.