科研 Skill
硬件样机开发路线规划
prototype-roadmap
Plans the path from idea to sellable product through EVT/DVT/PVT and mass production, with gates, durations, and long-lead purchases. Use to produce a dated roadmap.
SKILL.md
Prototype roadmap
Turn the design into a dated plan that a team can follow. Each stage has a deliverable and a gate. The plan shows the critical path and the date by which each long-lead part must be ordered. Write it to hw/roadmap.md.
Talk to the user in the user's language. Files are in English unless the user's 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
| File | What you take from it |
|---|---|
hw/brief.md | launch target, quantities, markets, budget |
hw/state.json | stage reached so far, gates already passed |
hw/bom.csv | lead_time_wk, stock_snapshot, lifecycle; custom parts (cell, molded parts, flex) |
hw/power/ | whether the power budget is measured or only estimated |
hw/compliance.md | certification durations and blocking items ("Schedule hooks") |
hw/cost/ | tooling and NRE lead times, MOQs |
hw/doability/review.md | open risks that need an experiment before a commitment |
Outputs
hw/roadmap/stages.json: stages, dependencies, duration ranges, gates, milestones and long-lead items. The format is intemplates/stages.example.json.hw/roadmap/schedule.mdandhw/roadmap/timeline.svg: generated byscripts/roadmap.py.hw/roadmap.md: the plan, built fromtemplates/roadmap.md, including the bring-up log.hw/state.json: the current stage and the next gate.
Procedure
-
Place the project. Decide which stage it is in: idea, Stage 0, Stage 1, EVT-n, DVT, PVT or MP. Use what has actually been built and measured. Do not use how finished the CAD looks: a collision-free 3D model means the industrial design is frozen, not the engineering.
-
Write the stages JSON. Start from
templates/stages.example.json, and remove the stages the product does not need. For example, a product with a catalogue cell has no custom-cell stage.- For each stage, give a
[best, worst]duration in weeks, its dependencies (depends_on, optionallag_weeks, negative for overlap) and an exit gate. Take the gates fromreferences/stages.md. - Use real lead times from
hw/bom.csv, supplier quotes andhw/compliance.mdwhere you have them. Tag each duration as verified or estimate. - Add a
long_leadentry for every part whose lead time is 12 weeks or more, or whose stock is low, with the stage that first needs it. - Give each
long_leadentryqty_neededand, when you have it, today's distributor stock:"stock": {"on_hand": 9278, "source": "LCSC", "date": "YYYY-MM-DD"}. When the order-by date from the factory lead time has passed but the stock coversqty_needed, the item is buy now from stock, not late. With too little stock or no stock data, it stays LATE and shows the shortfall. - Dependencies go in
depends_on. The script rejects unknown stage keys, so a typo such asafterfails loudly instead of silently starting the stage at week 0.
- For each stage, give a
-
Generate:
python3 scripts/roadmap.py --stages hw/roadmap/stages.json --md hw/roadmap/schedule.md --svg hw/roadmap/timeline.svgRead the critical path, the "LATE" rows and the "in stock: buy now" rows. Look at the SVG before you embed it: stage names wrap between words, and milestone labels take separate lanes so they never cover each other. Test the script with
python3 scripts/test_roadmap.py. -
Check the order of commitments. No custom cell, mold or board revision may start before the measurement that sizes it. If the plan has one, move it, or write down why the risk is accepted (
hw/decisions.md).- The usual critical path: power measurement → cell decision → custom cell → UN 38.3 → certification → sale.
- The final mold also waits for the cell envelope.
-
Write
hw/roadmap.md. The answer comes first:- where the project is now;
- the first legal sale, best and worst case, and what drives it;
- what to order now;
- the next gate.
Then give the timeline, the per-stage plans, an empty bring-up log and the schedule risks.
-
During EVT and later, use
references/bringup-checklist.mdfor each new board and log the results. Usereferences/test-fixtures.mdto plan test access before routing, and fixtures before PVT. -
Hand off.
cost-and-sourcingtakes the NRE timing and the long-lead purchases.doability-reviewtakes the stage the project is in and the uncommitted measurements.product-presentationtakestimeline.svgand the answer-first block.
Gate
The roadmap stage passes when:
- every stage has a deliverable, a duration range with an evidence tag and an exit gate;
- the critical path is identified, and no custom part starts before the measurement that sizes it (or the accepted risk is logged);
- every long-lead part has an order-by date, and late items are reported to the user;
- the first-legal-sale date is a range (best to worst), not a single optimistic date.
Taste and pitfalls
- Measure first. The first engineering deliverable is often a measurement bench, not a PCB. Current measured on a dev kit with the real duty cycle sizes the battery, the memory and the enclosure.
- The 3D model freezes the industrial design, not the engineering. Expect 3–4 board revisions and 1–2 mold iterations before mass production. Do not call a design "final" before it has been powered, measured, dropped and certified.
- Quote ranges, never single dates. Teams that promise the best case to customers end up refunding pre-orders.
- Order long-lead parts at once. Order EVT and DVT quantities as soon as a part is chosen. Lead times of 16–26 weeks are normal for springs, drivers and connectors, and stock can vanish.
- Certification is on the path, not after it. In markets like Brazil, nothing with a radio can be sold before homologation, and that includes a small launch batch.
- Design test access before routing: test pads, an RF test strategy and a test mode in firmware.
- Bring-up closes with numbers. Every checklist line records a measured value and the instrument. "Seems fine" does not close a line.
- Keep the roadmap honest. When a gate fails, move the dates and tell the user. Do not shrink later stages to keep the launch date.
References
references/stages.md: what each stage builds, the questions it answers and its gate, plus the critical path, long-lead parts and the iterations to expect.references/bringup-checklist.md: step-by-step board bring-up, from before power to the system soak.references/test-fixtures.md: design for test and the production fixtures, with NRE ranges.templates/stages.example.json: an example plan for a fictional BLE fitness band.templates/roadmap.md: the output template.
示例提示词
帮我规划一下从样机到量产的时间表和各阶段测试节点。
所属插件
安装该插件会一并获得同领域的 63 个 Skill / MCP。
同插件的其他科研 Skill
- ANDES电力系统动态仿真Runs ANDES power-system dynamic studies via PowerMCP: power flow, eigenvalue analysis, and time-domain simulation. Use for damping, stability, or oscillation-mode questions.
- 电池选型与电源预算Builds an evidence-tagged power budget and sizes a manufacturable battery with pouch outline, seals, and derating. Use when sizing runtime, mAh, charging, or supply rails.
- FPGA比特流生成与烧录Generates a Xilinx FPGA bitstream and programs it over JTAG, or burns an MCS image into flash for power-on boot. Use when flashing a board or diagnosing boot failures.
- 硬件项目发布包组装Assembles a hardware release package (fab files, BOM/CPL, carts, assembly guide, hashed manifest) and runs a ready-to-build gate. Use before ordering prototypes.
- 时钟域交叉风险审查Audits clock-domain-crossing risk on an FPGA design and applies the smallest safe synchronizer or constraint fix. Use to resolve CDC violations before sign-off.
- 硬件产品认证合规规划Plans certifications a hardware product needs per target market (FCC, CE/RED, UKCA, battery/radio rules), with cost and lead-time estimates. Use before PCB or enclosure tooling.
- Vivado XDC时序约束编写Authors a Vivado XDC timing constraint set from scratch: clocks, I/O delays, and timing exceptions. Use first, before timing closure, on a design with no or incomplete constraints.
- N-1/N-2应急违规处置Playbook for N-1/N-2 contingency violations: ranks contingencies and proposes preventive and corrective actions. Use after a study shows voltage or thermal problems.
- 潮流计算不收敛诊断Playbook for power-flow convergence failures in PSS/E, PSLF, PowerWorld, pandapower, PyPSA, surge, or OpenDSS. Use when a case diverges or fails to solve.
- 硬件成本核算与采购Prices a hardware product at multiple volumes with one-time vs per-unit cost, landed cost per country, and sourcing leads. Use to estimate unit cost before a pitch.
- RTL仿真覆盖率收敛Measures RTL simulation code coverage and iteratively closes it toward a target by adding testbench stimulus. Use for a sign-off-grade coverage report.
- 配电网DER接纳能力治理Playbook for distribution DER hosting-capacity limits: voltage rise, reverse flow, and thermal limits from PV and storage. Use to estimate how much DER a feeder can host.
- 电子电路设计与审查Designs, audits, or corrects an electronic circuit from a brief, schematic, or netlist, checking power domains, reset sequencing, and ratings. Use for circuit 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.
- 电力系统动态稳定处置Playbook for dynamic stability problems: poor damping, angle instability, or sustained oscillations from eigenvalue or time-domain studies. Use after an unstable study result.
- Egret电力市场调度优化Runs Egret market/operations optimization (DC-OPF, AC-OPF, unit commitment) via PowerMCP. Use for cheapest dispatch, unit commitment, or congestion checks.
- 电子元器件选型核查Researches electronic components against primary sources: part numbers, datasheet limits, lifecycle, stock, and price breaks, one dossier per part. Use to verify or source a BOM.
- EMC电磁兼容预测试Plans grounding, shielding, and filtering for EMC/EMI, and runs an emissions pre-scan with a root-cause fix sequence. Use before a lab test or after a failed EMI scan.
- 产品外壳参数化建模Designs a hardware enclosure as parametric CAD with STEP/STL/GLB output, a DFM check, and Blender assembly validation. Use when designing a case or checking fit.
- 电网频率响应问题处置Playbook for frequency problems: low inertia, high RoCoF, weak primary response, or UFLS risk after loss of the largest unit. Use when a study flags frequency issues.
- FPGA RTL到比特流全流程Drives a Xilinx FPGA design end to end through RTL, simulation, synthesis, implementation, and bitstream, gated at every stage. Use to run the complete build flow in one pass.
- 硬件产品全流程总协调Leads a physical electronic product from idea to a doable design, coordinating specs, parts, battery, PCB, enclosure, render, and cost sub-skills. Use starting a hardware product.
- 硬件原理图与BOM审查Reviews hardware projects: checks schematics against datasheets, pin connections, and firmware-to-hardware alignment across KiCad/Altium files. Use for a design alignment check.
- FPGA ILA在线逻辑调试Inserts an Integrated Logic Analyzer, programs the board, arms a trigger, and reads captured waveforms on real FPGA hardware. Use when sim passes but the board fails.
常见问题
硬件样机开发路线规划能做什么?
Plans the path from idea to sellable product through EVT/DVT/PVT and mass production, with gates, durations, and long-lead purchases. Use to produce a dated roadmap。
如何安装硬件样机开发路线规划?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「硬件样机开发路线规划」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
硬件样机开发路线规划需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
硬件样机开发路线规划经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。