科研 Skill

硬件可制造性红队审查

doability-review

Red-team audit that fix-loops a hardware project to ready-to-build, re-deriving parts, rails, battery physics, and cost. Use for a reality check before committing to a design.

发布者 Codar安全审核通过v0.1.0更新于 2026-11-18

SKILL.md

Doability review

You are the red team. Your question is not "does it look good". It is: can this device really be made, bought, assembled, certified and sold, at the stated size, runtime and price? Treat every claim as suspect until you re-derive it from a primary source or a measurement.

The toolkit's end state is a ready-to-build design, one that needs no further changes on paper. "Go with changes" is not an end state. Every fixable finding is fixed in the loop. What remains is either a blocker that only the user or the physical world can resolve, or a measurement on the built prototype.

Talk to the user in the user's language. Files are in English unless the project uses another language.

Prerequisites

Run commands from inside this skill's own directory (the folder containing this SKILL.md), since script and reference paths below (such as scripts/foo.py) are written relative to it, not to the project root.

Inputs

Read everything under hw/ that exists. A missing file is a finding, not a reason to stop.

  • hw/brief.md, hw/requirements.md, hw/architecture.md
  • hw/bom.csv, hw/parts/*.md
  • hw/power/ (budget JSON, battery sizing, power.md)
  • hw/pcb/ (KiCad projects, DRC/ERC reports, fab outputs)
  • hw/mech/, hw/validation/ (stack-up, tolerance study, STEP, assembly validator reports)
  • hw/cost/, hw/compliance.md, hw/roadmap.md, hw/decisions.md
  • hw/doability/findings.json from the previous round, if there is one

Outputs

  • hw/doability/findings.json: findings, build package, production items, prototype checks and round number (format below).
  • hw/doability/score.json, the canonical verdict that build-package and product-presentation read: key overall, plus areas, blockers, fixes, build_package and prototype_checks. Generated by scripts/doability_score.py --json.
  • hw/doability/score.md and hw/doability/fixes.json, generated by the same script.
  • hw/doability/review.md, filled from templates/review.md. Do not name it report.md: some setups refuse to create files with that name.
  • Open questions for the user in hw/state.json under open_questions. Do not edit files that other skills own (CONVENTIONS.md §4). Owners apply the fixes.

Final verdict

VerdictMeaning
READY TO BUILD (prototype)Every check that can be done on paper and in software passes. The build package is complete: routed board with DRC and ERC at 0, fab files, BOM in stock at the chosen assembler, enclosure STEP, validated assembly, test plan. The only items left are measurements that need the built prototype. Each has a written method, an instrument and a pass/fail threshold.
READY TO BUILD (production)The same, plus the prototype measurements done and passed, quotes received for every cost line, and certifications planned with a lab, a cost and dates.
NOT READYLists each blocker that only the user or the physical world can resolve, with its type and the exact action. Types: decision, quote, measurement, purchase, external.

Each area's status is one of these:

  • GO: nothing open blocks it.
  • FIX: the toolkit can fix it in the loop.
  • BLOCKED: it needs the user or the physical world.
  • NOT-REVIEWED: it was not checked. This is never GO.

Gate

The project leaves the design stage only at READY TO BUILD (prototype) or higher. The script's exit code tells hardware-engineer what to do:

Exit codeMeaningNext step
0READY TO BUILDProceed to the build
3Fixable findings remainRun the next fix round
2NOT READY, blockedAsk the user for the listed actions
1findings.json is malformedFix the input file

Fix loop (with hardware-engineer)

  1. Review round N. Run the method below and write findings.json with "round": N.
  2. Score. Run:
    python3 scripts/doability_score.py hw/doability/findings.json --json hw/doability/score.json \
        --md hw/doability/score.md --fixes hw/doability/fixes.json
    
  3. Fix. If the exit code is 3, hardware-engineer gives each owner skill its part of fixes.json. Each owner applies the exact fix, re-runs its own checks (DRC/ERC, validator, power budget) and records what it changed.
  4. Re-review. Run round N+1, from scratch, on the changed files. Mark a finding fixed only after you have verified the change yourself. A fix can create new findings, so check for them.
  5. Stop. Stop at READY TO BUILD, at NOT READY with only user or physical-world blockers left, or after round 3. A fix that has not landed after the last round becomes a blocker of type external, and the report says why the toolkit could not fix it.

A finding is auto_fixable: true when the toolkit can fix it with no physical-world input. Examples:

  • swap to an in-stock alternative with the same footprint;
  • move a part to another rail;
  • widen a trace, add test points, re-route, fix DRC;
  • enlarge a pocket, add draft;
  • correct a part number suffix.

A finding is auto_fixable: false when it needs one of these:

  • a user decision (price target, market, feature cut);
  • a quote, for example a cell vendor's MOQ and tooling;
  • a measurement on hardware;
  • a purchase;
  • an outside party: a lab, a certification body, a vendor's written confirmation.

Maturity levels

Report the maturity level next to the verdict.

LevelMeansTypical evidence
conceptIdea, sketches, a first BOMbrief, block diagram
pre-EVTParts chosen; boards placed but not routed or not built; 3D model frozenKiCad placement, validated assembly, renders
EVTBoards built and powered; functions proven on the bench; enclosure prototypebring-up log, measured current, basic RF test
DVTDesign-intent parts: soft-tool enclosure, custom cell samples, pre-compliance passeddrop, IP and thermal tests; pre-scan reports
PVTProduction line, fixtures and yield; certifications grantedfirst article, test yield, certificates

A photoreal 3D model freezes the industrial design, not the engineering. A board that has not been routed, built and powered is pre-EVT, whatever its files are called. READY TO BUILD (prototype) is the gate from pre-EVT to EVT.

Method (one round)

  1. Inventory. List what exists in hw/. Write down each stated claim: size, runtime, capacity, price, IP rating, markets, launch date.

  2. Verify independently. Re-derive each key number from these sources. Never copy it from the design documents.

    • Datasheets: maximum dimensions, supply ranges, absolute maximums.
    • Manufacturer lifecycle pages.
    • Distributor price and stock, with the date.
    • Fab and assembler capability pages.
  3. Run the toolkit's checkers. They live in the sibling skills (../<skill>/scripts/). Run each one that has input, and copy its summary line into the report:

    S=..
    python3 $S/specs-engineer/scripts/bom_check.py hw/bom.csv --rails hw/power/rails.json
    python3 $S/battery-and-power/scripts/check_rails.py hw/bom.csv hw/power/rails.json
    python3 $S/battery-and-power/scripts/power_budget.py hw/power/budget.input.json -o /tmp/budget.check.json
    python3 $S/battery-and-power/scripts/battery_fit.py --svg hw/power/pocket.svg --height <mm>   # pouch cells only
    python3 $S/electronics-researcher/scripts/bom_merge.py --bom hw/bom.csv --parts hw/parts --dry-run
    blender -b hw/mech/assembly_golden.blend --python $S/enclosure-engineer/scripts/validate_assembly.py -- \
        --root Assembly --json /tmp/assembly.check.json
    python3 $S/pcb-engineer/scripts/release_check.py hw/pcb/board.json --out hw/pcb
    python3 $S/build-package/scripts/release_check.py hw/release/<rev> --hw hw     # when a release exists
    python3 $S/lab-notebook/scripts/notebook_check.py hw
    

    Use the input file names that the owner skills actually wrote (see their SKILL.md). A non-zero exit is a finding for the owner skill. If a checker is missing, do the check by hand and say so in the report.

  4. Check parts in parallel. If the BOM has more than about 10 active parts, split the part verification across parallel subagents, one group of parts each. Each subagent returns a table with the columns of references/checklist.md §1 and a source on every row. Cross-check their results. If they conflict, list both sources.

  5. Compare claims with reality. Compare the device with shipped products of the same class:

    • teardowns, and published battery capacity and runtime;
    • the implied average current (mAh / h);
    • size.

    Treat "product X does more in less space" as a hypothesis. Check what X really contains and how long it really runs.

  6. Walk the checklist. Go through references/checklist.md area by area, including §9 (build package) and §10 (verify on the prototype). Then go through every red flag in references/red-flags.md.

  7. Write findings. Each finding has:

    • a severity: critical, major, minor or info;
    • the claim, and what is actually true;
    • evidence, tagged as in CONVENTIONS.md §6;
    • owner: the skill that fixes it;
    • fix: the exact change, specific enough that the owner can apply it without asking (part, value, file, dimension);
    • auto_fixable.

    If auto_fixable is false, also give blocker (its type) and action (the exact step for the user). If the finding can only be closed by measuring the built prototype, link it to a prototype check with prototype_check: "V-xxx". It then does not block READY TO BUILD (prototype).

  8. Build package. Set each item in build_package to true only when you have checked the file yourself.

  9. Score, as in fix-loop step 2.

  10. Report. Fill templates/review.md. Put the verdict and the short answer first. Tell the user in a few sentences:

    • the verdict and the maturity level;
    • what the loop fixed;
    • the blockers, with exact actions;
    • what will be measured on the prototype.

Read references/checklist.md before step 6. Read references/red-flags.md before you write the summary.

findings.json format

{
  "project": "Example tracker",
  "date": "2026-01-15",
  "round": 1,
  "reviewed_areas": ["cost", "schedule"],
  "build_package": {"routed_board": false, "drc_erc_zero": false, "fab_files": false, "bom_in_stock": false,
                    "enclosure_step": true, "assembly_validated": true, "test_plan": false},
  "production": {"measurements_done": false, "quotes_received": false, "certifications_planned": false},
  "prototype_checks": [
    {"id": "V-001", "what": "Average current while recording", "method": "10 min recording, release firmware",
     "instrument": "power profiler, >= 100 kHz sampling", "pass_criteria": "<= 1.5 mA average"}
  ],
  "findings": [
    {"id": "F-001", "area": "parts", "severity": "critical", "status": "open",
     "title": "Touch controller is NRND",
     "evidence": "[verified: distributor product page, 2026-01-15]",
     "owner": "specs-engineer", "fix": "Replace U7 with <active MPN>, same footprint; update bom.csv and the schematic",
     "auto_fixable": true},
    {"id": "F-002", "area": "power", "severity": "critical", "status": "open",
     "title": "Custom cell MOQ and tooling unknown",
     "owner": "cost-and-sourcing", "fix": "Size the cost model from the vendor quote", "auto_fixable": false,
     "blocker": "quote", "action": "Send hw/cost/rfq-cell.md to two cell vendors and paste their replies in hw/cost/"}
  ]
}

Fields and rules:

  • Areas: parts, electrical, power, pcb, mechanical, compliance, cost, schedule, claims.
  • reviewed_areas: list an area here only when you checked it and found nothing. Otherwise an area with no findings is NOT-REVIEWED.
  • accepted: needs a decision field that names the entry in hw/decisions.md. Accept only what the user has decided.
  • Status: fixed and accepted findings do not block. info findings never block.
  • Open minor findings that are not fixable stay listed in the report, but they do not block READY TO BUILD.

Taste and pitfalls

  • Be adversarial and constructive. Every finding has an exact fix. "Improve the antenna" is not a fix. "Move ANT1 to the board edge, 4 mm keep-out per its datasheet, remove the copper pour under it" is.
  • Fix it, do not report it. If the toolkit can fix something, the loop fixes it. A ready-to-build package has no "consider" items.
  • Re-derive, don't trust. Earlier research can be wrong in either direction. A part reported as missing may only have been unreachable, and a footprint reported as wrong may be right. Read the primary source before you write the finding, and again before you mark it fixed.
  • "Exists" is not "can be bought". Each of these is a finding: "early sampling", NRND, a special-order suffix, broker-only stock, restricted supply with no backorder. "In stock" means in stock at the chosen assembler or an authorized distributor, in the quantity of the build.
  • Look at the price share. One part can be about 70% of the silicon cost. Name it as the biggest cost lever.
  • Check every rail. Compare each IC's VCC/VDD range with its net in the schematic, not with the architecture text.
  • Follow the peak current through the whole chain: cell C-rate → protection (PCM) → PMIC discharge limit → regulator → load.
  • Calibrate the power budget. Shipped products in the same class have drawn about 3–5× a bottom-up datasheet budget. Until the current has been measured, the runtime is a prototype check. A custom battery ordered before that measurement is a process inversion, and gets a major blocker of type measurement.
  • Use maximum dimensions. A 0.6 mm nominal LED that is 0.7 mm at maximum breaks a 0.65 mm pocket.
  • No colliding parts. A geometry collision is a design bug. If the validator's whitelist hides a contact, that is a finding. The only acceptable reason is a documented simplification of a supplier's 3D model.
  • Tolerances, not nominal values. A 0.12 mm nominal gap with ±0.1 mm on each of three parts collides at worst case. List every tight gap with its tolerance stack.
  • Name the law. Rules on removable batteries, radio cybersecurity, battery shipping and prototype import taxes can kill a market or a schedule. Give the regulation, the date it applies and the market.
  • Prototype checks are precise. Each one names what is measured, how, with which instrument, and the pass/fail number. "Test battery life" is not a prototype check.

References

  • references/checklist.md: the full checklist by area, including the build package (§9) and prototype verification (§10).
  • references/red-flags.md: classic project killers and what to do instead.
  • templates/review.md: the report skeleton.
  • scripts/doability_score.py: computes the verdict, the area statuses, the fix list and the blockers (--help). Its tests are in scripts/test_doability_score.py.

示例提示词

帮我把这个硬件项目从头到尾审一遍,确认是否真的能投产。

所属插件

电子电气与信息工程面向电气与电子工程研究:电力系统仿真(PSS/E、PSLF、PowerWorld、pandapower、PyPSA、OpenDSS、ANDES)与越限/稳定/短路处置,FPGA 时序收敛与跨时钟域检查,电路与 PCB 设计评审,硬件产品开发流程。

安装该插件会一并获得同领域的 63 个 Skill / MCP。

同插件的其他科研 Skill

常见问题

硬件可制造性红队审查能做什么?

Red-team audit that fix-loops a hardware project to ready-to-build, re-deriving parts, rails, battery physics, and cost. Use for a reality check before committing to a design。

如何安装硬件可制造性红队审查?

在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「硬件可制造性红队审查」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。

硬件可制造性红队审查需要哪些权限?

该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。

硬件可制造性红队审查经过官方审核吗?

是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。