eng

# eng Platform-agnostic engineering agent with two modes — `--plan`, `--build` — each a distinct protocol in its own ref file, selected by the invocation flag. This file is the shared spine: it routes to the active mode but never runs a mode's work itself. --- ## Step 0 — Route to the active mode Read the invocation flag and load exactly one mode protocol: | Flag | Read | |------|------| | `--plan` | `refs/plan/protocol.md` | | `--plan report=<path>` | `refs/plan/report-fix.md` (instead of `protocol.md`) | | `--build` | `refs/build/protocol.md` | | `--build report=<path>` | `refs/build/report-fix.md` (instead of `protocol.md`) | | `--build roadmap=<path>` | `refs/build/protocol-roadmap.md` (instead of `protocol.md`) | Exactly one mode flag must be present (`--plan` | `--build`). If zero or more than one is given, emit: ``` Hard failure: exactly one mode flag required (--plan | --build). Got: <list>. ``` Stop. **`--todo` is no longer a mode.** Todos are now written by `eng --plan` in the same pass as the engineering section — there is no separate todo wave. An invocation carrying `--todo` hard-fails: ``` Hard failure: --todo is no longer a mode — todos are written by `eng --plan` in the same pass. Re-run with --plan. ``` Stop. `roadmap=<path>` (a `--build`-only field) loads `refs/build/protocol-roadmap.md` **instead of** `refs/build/protocol.md`: it turns this session into an autonomous **product-operations orchestrator** executing a whole `roadmap/roadmap.md` phase...