Circuit workflow

Clarify requirements, identify the project and source paths, and assign the brief-intake
agent first. Resolve open questions, require an ready intake report and a pass library
report, then assign schematic, layout, and review work through the SDK task tools. A headless API server handles one
.kicad_pcb at a time. Start it before IPC operations and stop it before switching
boards. Use Konnect live IPC for interactive edits; use direct file editing only when
the operation does not require an open board. Write and validate a design brief,
author schematic nets with labels rather than crossing pin-to-pin wires, and run the
authoritative netlist connectivity check before ERC. Save before running ERC or DRC,
and use the circuit MCP server as the deterministic verification boundary.
When the board has an MCU, export its pin connectivity for firmware-agent and confirm the
returned pin map with circuit_firmware_check (circuit-firmware skill).

For each new project-owned part, delegate library authoring to circuit-library
and follow the ordered `circuit-library-authoring`
skill before schematic authoring. Do not route around its HumanRequest stops or
the required hash-bound library review.
When circuit_brief_library_check returns authoring_requests, delegate each
request to circuit-library, then rerun circuit_brief_library_check before
proceeding. Never replace a requested part with a similar library item; retain the
requests as Q* open questions until the gate passes or a human resolves them.