englisted

Platform-agnostic engineering agent with three modes: --plan (propose file changes for human approval AND write the per-feature todo tickets in the same pass), --build (write code from the todo tickets — the single and final build spec), --review (one adversarial whole-change review of the working diff, run by a separate reviewer subagent — spawned by --build automatically, and available standalone on any branch at any time). Use --review when the user says "review this change", "review my diff", "code review this branch", or invokes /eng --review. Invoked by plan-em or directly by the user.
ndisisnd/msg · ★ 6 · AI & Automation · score 79

Install: claude install-skill ndisisnd/msg

# eng Platform-agnostic engineering agent with three modes — `--plan`, `--build`, `--review` — each a distinct protocol in its own ref file, selected by the invocation flag. This file routes; the shared spine that runs for every mode is `refs/protocol-core.md` (Steps 0–6), and it never runs a mode's work itself. ## Routing (Step 0 — full rules in `refs/protocol-core.md`) Read the invocation flag and load exactly one mode protocol: | Flag | Read | |------|------| | `--plan` | `refs/plan/protocol.md` | | `--plan report=<path>` | `refs/plan/fix-plan.md` (instead of `protocol.md`) | | `--build` | `refs/build/protocol.md` — **unless an orchestrator spawned you as a build packet**, in which case read `refs/build/protocol-packet.md` instead and stop; it is the whole leaf contract | | `--build report=<path>` | `refs/build/fix-build.md` (instead of `protocol.md`) | | `--review` | `refs/review/protocol.md` | **Natural-language triggers for `--review`:** "review this change", "review my diff", "code review this branch", "adversarial review", "look for bugs in what I just wrote". Anything asking for *style, naming or standards* is `/cook`, not this mode. **`--quiet` / `--status <n>m`** (`--build` only) — heartbeat control; flag beats policy beats default (`../shared/refs/status-heartbeat.md`). Exactly one mode flag must be present — zero, several, or the retired `--todo` hard-fail with the exact messages in `refs/protocol-core.md` § Step 0. Then read the active mode file **fully**