用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/a5c-ai/babysitter --skill design-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Reference for querying the Atlas knowledge graph through its MCP tools — the SECONDARY enrichment/comparison layer that adds best-practice context to systems you have ALREADY scanned from your real sources (`az`, repos, dirs). Use when you need to look up nodes, edges, kinds, clusters, stats, or wiki pages in Atlas to compare against your real inventory. (atlas graph, query atlas, atlas mcp, search the graph, graph neighbors, atlas record, atlas kinds, enrichment layer)
Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
正在显示 SKILL.md
基于 SOC 职业分类
| name | design-review |
| description | Skill for formal design review preparation and execution (PDR/CDR) |
| allowed-tools | ["Read","Write","Glob","Grep","Bash"] |
| metadata | {"specialization":"mechanical-engineering","domain":"science","category":"design-review-documentation","priority":"medium","phase":7,"tools-libraries":["PLM systems","Requirements management tools","Presentation tools"]} |
| graph | {"domains":["domain:mechanical-engineering"],"skillAreas":["skill-area:physics-simulation","skill-area:mathematical-reasoning","skill-area:motion-planning"],"roles":["role:systems-integration-engineer","role:research-engineer"]} |
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"
}
]
},