This roadmap is reconciled against the shipping code. The Shipped list is what actually works in
v0.1.0 today. The Closing the doc↔code gap section tracks behavior that the docs, README, or a command’s help imply but the code doesn’t do yet — we track these explicitly so the docs never describe something that isn’t real.Shipped — v0.1.0 (May 2026)
AI design
chat, ask, agent, plan, review, signalLocal validation & export
erc, drc, gerbers, export (pdf/svg/netlist/bom/step/pos), engineConversion
convert (Altium ↔ KiCad ↔ .trace_sch/.trace_pcb), netlist-accurate Altium importOffline helpers
index, rules, historyParts & manufacturing
components, bom, generate, dfm, order (status/list/checkout/cancel/freight)Account & teams
auth, whoami, versions, teams, billing, shareIntegration
byok, mcp (12 tools + 4 prompts), altium bridge, config, doctorDistribution
pip, Homebrew, npm, GitHub Action, Python SDK (
buildwithtrace-sdk), Node SDK (@buildwithtrace/sdk)Closing the doc↔code gap
These are referenced in the README, the docs, or a command’s help/flags, but aren’t fully implemented yet. They’re the highest priority because shipped docs should never describe behavior that doesn’t exist.| Gap | Status today | Target |
|---|---|---|
order submit | Stub — prints guidance, no real submission | v0.2.0 |
versions diff | Not built (README implied “diff”) | v0.2.0 |
teams switch + member management | Only list/create/invite | v0.2.0 / v1.2.0 |
erc/drc --format json|markdown, --output, --strict, --rules, --category | Only --exit-zero | v0.2.0 |
review --format, --severity | Only --output/--scope/--focus | v0.2.0 |
ask --format/--output honored end-to-end | Partial | v0.2.0 |
export manufacturer presets, --zip fab bundle, --validate, --layers | Not built | v0.3.0 |
| Export formats: ODB++, IPC-2581, DXF, PostScript | Not built | v0.3.0 |
components check --distributors add ti, amazon | jlcpcb/lcsc/digikey/mouser only | v0.2.0 |
init — project scaffolding + templates | Not built | v0.3.0 |
Variant-aware CLI export (--variant) | GUI-only | v1.1.0 |
Polish backlog
Beyond new commands, a running list of UX/reliability refinements is tracked (terminal-experience and EDA-validation quality), prioritized across v0.2–v0.3:- Rendering: colored pin types, top/bottom pin rows, multi-unit symbols, terminal-width-aware boxes, QFN/BGA footprint visuals
- Input: multiline prompts, input history,
stdinpiping (cat x.kicad_sym | buildwithtrace ask …), path tab-completion - Output:
--quiet/--verbose, generation progress, clickable file paths, diff view for edits, context-window usage - Auth: token-expiry warnings, multi-account
--profile - Reliability: resume an interrupted stream, explicit proxy support, upload progress
- Workflow: git-aware auto-branch +
undo,watchmode, pipeline chaining,.tracerc, saved templates, shell completion - EDA validation: pin-count vs datasheet, KLC checks, footprint↔symbol matching,
.kicad_symversion compatibility
Upcoming
v0.2.0 — Manufacturing pipeline + scriptable checks
Real
order submit + order track; versions diff; teams switch; structured --format/--output for erc/drc/review/ask; autoroute; annotate; resume interrupted generations; shell completions.v0.3.0 — Placement/routing intelligence + richer export
place, route, impedance, stackup, thermal; init scaffolding; manufacturer export presets + fab bundles (ODB++/IPC-2581/DXF/PS); .trace/context.md AI memory.v0.4.0 — Simulation + signal integrity
simulate (ngSPICE ac/dc/tran); si for true signal-integrity analysis (eye diagrams, crosstalk) — distinct from today’s signal path tracing; power; watch mode.v1.0.0 — Production hardening
Full docs↔code parity;
ci one-command validation; CI/CD templates; Windows Action runner. (The Node.js SDK on npm has shipped — @buildwithtrace/sdk.)The canonical roadmap lives in the CLI repo’s
ROADMAP.md and is kept in sync with this page. If you find a command documented here that doesn’t behave as described, that’s a bug — please report it.