Keitark/pcba-design-skills / .agents/skills/plan-electronic-product
plan-electronic-product
VerifiedTurn an electronic product idea, behavior description, reverse-engineering note, or incomplete circuit concept into a decision-ready engineering brief and architecture. Use before schematic design or audit when functions, operating states, power, interfaces, mechanics, production quantity, cost, or measurable requirements are missing or ambiguous.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 2.4 KB |
| agents/openai.yaml | config | 266 B |
| assets/product-brief.yaml | config | 568 B |
| references/intake-checklist.md | markdown | 1.6 KB |
references/intake-checklist.md
View on GitHub# Electronic-product intake checklist
## Product and environment
- User problem, success behavior, prohibited behavior, and intended operator.
- Indoor/outdoor, temperature, humidity, vibration, ingress, cable length, and
expected lifetime.
- Prototype quantity, production quantity, target board and assembled cost,
schedule, repairability, and component-lifecycle expectations.
## Electrical architecture
- Every power source, connector, nominal range, transient condition, source
capability, reverse-polarity or back-power risk, and required isolation.
- Rails and modes: off, startup, programming, normal, sleep, reset, fault, and
partial-power states.
- External and internal interfaces with direction, voltage domain, data rate,
likely edge rate, topology, loading, hot-plug behavior, and protection.
- Shared buses or memories with one explicit owner per state and hardware-safe
defaults before firmware starts.
## Physical architecture
- Board outline, mounting, enclosure, connector location, controls, indicators,
antenna, thermal paths, keepouts, clearances, and assembly side limits.
- Programming, boundary/test access, debug connectors, measurement points, and
replaceable or field-serviceable elements.
## Evidence classes
- `SPEC`: authoritative requirement, standard, official datasheet, or approved
measured result.
- `TARGET`: project allocation chosen with stated margin.
- `ASSUMPTION`: temporary premise that must be confirmed before its gate.
- `TBD_MEASURE`: quantity that must be measured on the physical system.
Every unresolved item needs an owner, affected stage, and the evidence that
will close it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |