EE BOM Finalizer

Use this skill after component selection and before BOM export or hardware BOM persistence.

Core Workflow

1. Read references/hardware-bom-schema.md, references/sourcing-evidence-contract.md, and references/finalization-contract.md.
2. Inspect selected_components, alternatives, and supply_risks.
3. Enrich missing purchasing fields with catalog detail lookup. For exact LCSC/JLC or manufacturer part numbers, use parts.detail so supplier parameters, datasheet URLs, cached datasheet PDFs, image URLs, and JLC SMT library status are preserved.
4. Re-validate required fields.
5. After writing the first BOM, resolve specific open identities, variants, quantities, interfaces, or other user-owned BOM choices with user.ask purpose="bom_item_confirmation". Write every answer back and repeat only while concrete design-critical items remain.
6. Never ask the user to approve, reject, review, or revise the whole BOM. Set bom_ready true only after design-critical items are resolved.
7. Export only when the BOM is ready or the user explicitly accepts known gaps.
8. Report the BOM written and invite the next stage in ordinary final text. Stop the query unless its original scope explicitly requested later stages.
9. For electronics that will become a schematic, hand off the ready BOM to electrical implementation research and the real tscircuit draft only when a later query authorizes that work. BOM readiness means “what to buy” is known; it does not authorize pinout-only wiring.

Never hide unresolved items. If required data is still missing, return bom_ready: false with mitigation steps.

References

• references/hardware-bom-schema.md - shared row schema for component selection and final BOM files.
• references/sourcing-evidence-contract.md - authoritative supplier identity, unresolved named-part, and JLC SMT library rules.
• references/finalization-contract.md - validation rules, enrichment loop, export rules, and output contract.
• Load the component-selection skill for the upstream component selection contract.
• Use pcb.run(profile="check") for the current routed/DRC evidence. pcb.run(profile="release") reuses that Build when current, exports every deliverable into one package, runs the Host-owned independent Release Review, and publishes on Pass or Warning; only Blocked refuses release.