科研 Skill
硬件产品需求访谈
product-discovery
Interviews the user to turn a vague hardware idea into a written brief covering use, size, connectivity, battery, and quantities. Use at the start of a hardware project.
SKILL.md
Product discovery
Turn an idea into a brief that every later stage can design against. The brief records what the user wants, and what each wish costs physically. Reality checks come later. This stage makes sure the wishes are explicit, measurable and ranked.
Talk to the user in their language. The files are written in English unless the user asks otherwise.
Inputs
- The user's first description, any reference images, sketches or SVG outlines, and products they mention.
hw/brief.mdandhw/decisions.md, if they exist (re-interview only what is missing or changed).
Outputs
hw/brief.md, fromtemplates/brief.md. Keep its headings exactly; other skills parse them.hw/decisions.md: one entry per decision made in the interview (D-001, date, decision, options considered, reason, decided by).hw/refs/: every reference the user gives, copied with a short name. This covers images, sketches and SVG outlines (for example the top-view shape of the device or of a part), plushw/refs/README.md, which lists them with one line each.hw/state.json: setstages.discovery = "done"after the gate. Add any unresolved items toopen_questions.
Procedure
1. Read before you ask
Extract everything the first message already answers. Restate the idea in two sentences: the job the product does, and the moment of use. Never ask a question the user already answered.
2. Interview in rounds
Use AskUserQuestion, with at most 4 questions per call and at most 4 rounds in total when possible.
-
Put the recommended option first and mark it "(Recommended)". The user can always pick "Other".
-
Use
previewwhen the user compares shapes, sizes or layouts. ASCII top views with dimensions work well:┌──────────┐ 28 × 28 × 9 mm │ ◯ LED │ pendant, cord loop on top └──────────┘ -
Ask only questions that change the product. For everything else, state the default you are taking and log it as a decision. The full bank, with the reason for each question and its typical default, is in
references/question-bank.md. Read it before round 1.
Suggested order (merge rounds when answers are already known):
- Use. What it does, who uses it, where and how it is carried or mounted, the moment of use, and the products the user admires.
- Body. Size and shape targets, whether size is the top priority, weight, interaction (buttons, touch, LED, sound, haptics), look and finish (colors, transparent variant, materials).
- Life. Battery-life target for each mode (in hours), standby, charging method, connectivity and phone pairing, offline storage, sensors, ingress target.
- Business. Markets where it will be sold, quantities and dates (first prototype, first batch, 1k, 10k), unit-cost target, NRE budget.
Read references/use-environments.md once the environment is known. It turns "worn on the chest", "used in the shower" or "for kids" into concrete requirements.
3. Be honest about physics, gently
When a wish is expensive, say it once, in one or two sentences, with numbers. Offer two or three options. Record the user's choice; never refuse. Typical cases:
- Continuous operation in a tiny body. A coin-sized pendant holds about 0.2–0.3 Wh. Twenty-four hours of continuous audio recording needs an average draw of about 2–3 mA. That is possible only with firmware designed for it from day one.
- Options: shorter life, a bigger body, or recording triggered by an event (voice, touch).
- Wi-Fi or cellular in a tiny body. Peaks of 250–400 mA exceed what a small cell and a small PMIC can deliver.
- Options: BLE only (the phone relays the data), a bigger cell, or Wi-Fi only on the dock.
- IP68 with many openings. Every port, button and seam is a sealing problem.
- Options: membranes, molded contacts, capacitive touch instead of buttons, fewer openings.
- Wireless charging in a tiny body. It adds a coil, heat and thickness, and charges no faster than the cell's own limit allows.
- Options: magnetic pogo or molded contacts with a dock.
- "Product X does more in less space." Accept the reference, and plan to check it with data (teardown, FCC photos, spec sheet) in
doability-review. Big companies use custom silicon, custom cells and stacked boards.
4. Turn wishes into a seed table
Write every wish as a measurable target with priority must, should or nice, the reason, and where it came from. "Small" becomes "≤ 30 × 30 × 9 mm, size is priority 1". "Long battery" becomes "≥ 12 h recording + 7 days standby". specs-engineer turns this table into REQ-xxx.
Rank the top three priorities explicitly (for example size > battery life > cost). Later trade-offs use this ranking instead of asking the user again.
5. Gate: the user approves the brief
Show a short summary in chat:
- the idea in two sentences;
- the top three priorities;
- the five to eight key targets;
- the costly trade-offs and what was chosen;
- the defaults you took;
- the open questions.
Ask with AskUserQuestion: "Approve the brief", "Change something", "Add something". Iterate until approved. Then set the state, and hand over to hardware-engineer (or to specs-engineer if the user is running the stages manually).
Taste and pitfalls
- Do not interrogate. Four rounds of four questions is the maximum, not the target. A clear first message may need one round.
- Do not ask what a default answers well. For example: USB-C vs. contacts for a desk device, or the BLE version. State the default and log it.
- Ask what only the user knows. Where it is worn, which markets, how many units, what it must feel like, which compromise hurts least.
- Numbers, not adjectives. Every target has a unit and a limit, in mm, hours, grams, IP code and USD.
- Separate modes. "Battery life" means nothing until each mode has a duration (active, connected idle, standby, shipping), and each mode costs a different current.
- Never round a wish into something easier without saying so. If you propose 12 h instead of 24 h, it is a decision with a reason, logged.
- Keep the user's references as given. An SVG outline the user drew is a design input. Store it unmodified, and redraw it only on request.
- A shape must stay buildable. A battery outline is a pouch with straight edges and a sealed border. An enclosure has draft and minimum walls. Note this in the brief when the user's shape conflicts with it, and let the later stages solve it.
- Variants are real cost. Each color or transparent variant needs its own material, molding and validation, and may need its own render. Ask how many variants the first batch has.
- Markets decide certification. "Worldwide" is not an answer. Ask which first markets ship in the first year.
示例提示词
我想做一个智能硬件,帮我通过访谈把需求写成项目简报。
所属插件
安装该插件会一并获得同领域的 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.
常见问题
硬件产品需求访谈能做什么?
Interviews the user to turn a vague hardware idea into a written brief covering use, size, connectivity, battery, and quantities. Use at the start of a hardware project。
如何安装硬件产品需求访谈?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「硬件产品需求访谈」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
硬件产品需求访谈需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
硬件产品需求访谈经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。