KiCadRoutingTools (KiCad MCP routing skill)ECADConfidence: Medium

The Planes tab's Create Planes ignored screenshot-verified Net to Layer Assignments and poured both the GND and +5V zones onto F.Cu instead of the assigned In1.Cu and In2.Cu, while the dialog reported success. Re-running made it worse: it added two more zones, same nets, same wrong layer, so DRC then reported zones_intersect on top of dozens of unconnected items.

Impact Analysis

Persona

Electrical Engineer

Team Size Impact

5x Multiplier

Prototype Delay

2 Days

Est. Annual Cost

$18,000

1 user · 1 month240 min
Rest of team960 min
Rest of year13,200 min

monthly_minutes × 12 × team_multiplier ÷ 60 × $75/hr = $18k/yr

$75/hr assumed rate.

Annual team-minutes decomposed from the reported monthly inputs.

Evidence & Sources

1 Sources

KiCadRoutingTools issue #1056: Planes tab pours zones onto outer layers (F.Cu/B.Cu) regardless of Net -> Layer Assignments / Target Layers; reruns add duplicates instead of replacing

github.com

→

Analyst Notes

From the Grok Haitch pain-radar compilation, finding 37, found 2026-09-27, score 9/10. Verbatim evidence: the dialog reports "Plane creation complete! Planes poured: 2 zone(s) on 2 net(s)" while both zones landed on F.Cu. Cost model assumes the zones are moved to the correct layers by hand and the duplicates deleted.