PCB-Agent-Teams — KiCad PCB Workflow

English · 中文

Describe the board you want. Get back a KiCad project and a fab-ready Gerber package — with every part checked against live distributor stock, and every stage cleared by scripts, SPICE and DRC rather than by the model’s own say-so.

Under the hood: a multi-project PCB workspace built on KiCad 10, where ten skills drive a Phase 0–5 pipeline covering the full chain from topology discussion to Gerber shipout.

What a run looks like

You:  I need an isolated 400 V DC-bus voltage sensor — 0–3.3 V out to an MCU ADC.

/circuit-design        topology fixed: isolated amplifier + staged HV divider, anchor parts named
/component-selecting-* 3 live candidates per part — all in stock, all with a ready KiCad library
/component-preparing   datasheets fetched, symbols + footprints + 3D vendored, BOM locked
/draw-schematic        .kicad_sch generated from Python source, ERC clean
/check-schematic       divider ratio re-simulated in SPICE, every pin cross-checked vs datasheet
/draw-pcb              HV/LV zones split, isolation barrier held, GND poured, DRC clean
/check-pcb             44 EMC rules + thermal + parasitics + schematic↔PCB netlist diff
/release               Gerber + CPL + production BOM + ORDER_GUIDE.md, zipped for the fab

You are never locked into that sequence — every step is a toolbox you can run, redo, hand-edit or skip.

Before you read on — two things to know

1. KiCad 10 is required, and macOS is the only platform this has been tested on. The skills call kicad-cli and KiCad’s bundled pcbnew Python API directly. Linux is wired up but unverified — the interpreter probe includes /usr/lib/kicad/python3, and kicad-cli resolution covers Flatpak, Snap and Nix. Windows is the real gap: kicad-cli resolves there, but no pcbnew interpreter path ships, so the board-writing steps in draw-pcb have nothing to call. Details in Prerequisites.