adom-wiki pkg install adom/kicad-bridge
adom-wiki pkg install adom/codex
adom-codex context

# Route the public Adom BMS with Codex and Astra

The largest board in this progression is the public [BQ76952 BMS Molecule v2](https://wiki.adom.inc/adom/molecule-bq76952-v2). Its source has 353 footprints and four copper layers. Preserve the original project and work on a separately named copy.

## Prerequisites verified for this recording

- Adom Hydrogen with **Codex** and **Astra** explicitly selected.
- A connected Windows Adom Bridge and KiCad 10.0.1 or newer with the IPC API enabled. The recording host has KiCad 10.0.5.
- **Insiders KiCad Bridge 0.9.347**, verified both in the release manifest and on ConfRoomROG. This is an insiders workflow; the old public 0.9.317 release does not provide this routing capability. Verify the installed version before starting. A newer release should be checked against its current verb catalog.
- Shared KiCad Bridge skills, package **1.0.133** at verification, plus Adom Codex **0.1.19**. Package versions and desktop bridge versions are separate.
- Your manufacturing rules, layer stackup, copper thickness, operating voltages and load requirements. This example uses Adom copper ablation, the existing four 35 micrometre layers, a 48 V intended pack and a 72 V / 6 A design basis. The 0.1 mm ablation kerf is a process capability, not a universal electrical isolation gap.

Install the shared skills in the Hydrogen workspace:

```bash
adom-wiki pkg install adom/kicad-bridge
adom-wiki pkg install adom/codex
adom-codex context
```

Start a new Codex conversation after installation, or explicitly ask the existing conversation to read the installed skills. Installing files does not replace instructions already loaded in a running thread. The bridge skills describe the general KiCad verbs; the Codex electrical-routing skill adds the engineering workflow. These are reusable skills, not a packaged universal autorouter.

## Copy this prompt into Hydrogen

**Manually paste the prompt below.** Automatic dashboard “Send to AI” delivery has not passed our end-to-end test, so this guide does not depend on it.

> Read the installed codex-adom, codex-adom-electrical-routing and KiCad Bridge skills. Establish the container and Windows host through Adom Bridge, use an explicit target and AI thread identity, and inspect current ownership, KiCad version, bridge version and board state before editing.
>
> Use the public Adom BQ76952 BMS Molecule v2 at https://wiki.adom.inc/adom/molecule-bq76952-v2. Download the project with `adom-wiki repo clone adom/molecule-bq76952-v2 --dir ./bms-reference`, including `Molecule_BQ76952 - v2.kicad_pcb`, its `.kicad_pro`, the root schematic and all referenced schematic sheets. Preserve that directory. Make a new working copy with a different name and deliver it to the selected Windows host through Adom Bridge.
>
> Inspect the schematic, assembly variants, pad nets, heat sources and exposed pads before routing. For this example use our confirmed Adom copper-ablation process, existing four 35 micrometre copper layers, intended 48 V pack and 72 V / 6 A design basis. Preserve stricter existing electrical rules. Explain any missing plating, insulation, thermal, load or interface requirement instead of silently assuming it.
>
> Show the original human-routed board, navigate its monitor, shunt, power FET and interface sections, then remove all board routing from the copy. Remove original traces, vias, copper zones and board-level copper graphics while preserving component placement, footprint copper, net ties, rule areas and the original project. Read back the empty state; cached fills must not count as remaining connections. Respect the per-call removal limit and use revision-checked batches.
>
> Calculate fresh routes with Astra-authored planning and geometry checks. Do not use Freerouting or another external autorouter, and do not reconstruct the original trace coordinates. Prefer horizontal, vertical and 45-degree segments, short local decoupling connections and deliberate layer changes. Plan neighboring dense pin escapes together. Preserve Kelvin shunt sensing, distinct VSS/PGND/QGND domains and the USB pair's reference path. Preserve assembly variants rather than assuming DNP FETs share current.
>
> Allocate connected power and thermal copper on the actual pad nets, retain useful copper for ablation, and inspect necks and via transitions. Do not solve a 6 A return with a thin signal trace or a lone small via merely to erase a ratsnest. Refill and run native DRC on disposable candidates, preserve accepted checkpoints, reject new violations, and check the uncapped connection count and report-truncation flags.
>
> Once the candidate is ready, record a native KiCad window replay through Adom Bridge. Explain what was calculated beforehand. Commit the exact accepted paths with `kicad_route_net` and `expectedRevision`; use native KiCad IPC for zone operations where no specialized bridge verb exists. Validate and save the actual replay. Give me the resulting board, evidence, and a clear account of remaining physical qualification work. If making a video, use Adom TTS, show routing action at 10x, label inspection holds separately, and open the finished MP4 on my Windows host through Adom Bridge.

The prompt requests a new engineering run. It does not promise the same path geometry, run time or validation result on a different design or environment.

[Watch the progression and detailed films](https://wiki.adom.inc/adom/codex/files/docs/ASTRA-KICAD.md).