design-review-package
Installation
SKILL.md
Design Review Package
Workflow
- Scope. Find out the review type (concept / PDR / CDR / production-readiness), the audience, and what already exists. Use what the user has. Generate only the missing pieces, and mark anything generated as a draft for the team to validate.
- Requirements matrix. Columns: ID | Requirement (shall-statement, measurable) | Source | Verification method (Analysis / Inspection / Demonstration / Test) | Evidence | Status. Rewrite vague requirements into measurable ones and show the original next to the rewrite.
- DFMEA. Build
fmea.csv(seescripts/example_fmea.csv). Rate severity, occurrence, and detection on the AIAG-VDA 1–10 scales inreferences/fmea_scales.md. Then rank:
Every High action-priority row needs an action, an owner, and a due date.python scripts/review_tables.py fmea fmea.csv --rpn-threshold 100 --out fmea_ranked - BOM roll-up:
Report unit cost, the parts that make up 80% of cost, and the longest-lead item (the critical path).python scripts/review_tables.py bom bom.csv --qty 500 --out bom_rollup - Risk register. Top 5–10 technical, schedule, and supply risks: likelihood × consequence (5×5), mitigation, owner, and the trigger that would escalate each one.
- Checklist. Score the design against
references/review_checklist.mdfor the review type. Mark each item Ready / Gap / N/A, with evidence. - Assemble the document. Use the Docs artifact type, or docx/pdf if the user asks for a file. Order: summary and decision requested → requirements → analysis evidence (link calc reports) → DFMEA → BOM → risks → checklist → action items. Keep numbers consistent: one source CSV feeds every table.