ndisisnd/msg / .claude/skills/eng
eng
UnverifiedPlatform-agnostic engineering agent with four 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), --bug "<what is wrong>" (file a bug you found by hand as a new numbered report in the PRD's reports/ folder, then fix it with the normal fix flow). Use --bug when the user says "I found a bug", "report a bug", "this is broken", or invokes /eng --bug. 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.
eng
Platform-agnostic engineering agent with four modes — --plan, --build, --review, --bug. This file routes. The shared spine for every mode is refs/protocol-core.md (Steps 0–6); it never runs a mode's work itself.
Routing — the one routing table
Read the invocation flag and load exactly one mode file:
| Flag | Read |
|---|---|
--plan | refs/plan/protocol.md |
--plan report=<path> | refs/plan/fix-plan.md |
--build (manual run) | refs/build/protocol.md, which runs the build loop in refs/build/protocol-packet.md |
--build (spawned by an orchestrator as a build packet) | refs/build/protocol-packet.md only — it is the whole leaf contract; stop reading here |
--build report=<path> | refs/build/fix-build.md |
--review | refs/review/protocol.md |
--bug "<what is wrong>" | refs/build/bug-report.md — writes the bug as a new report, then runs --build report= on it |
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 about style, naming or standards is /cook, not this mode.
Progress messages (--build) are always on, every 5 minutes (../shared/refs/status-heartbeat.md).
Exactly one mode flag must be present. Zero, several, or --todo hard-fail with the messages in refs/protocol-core.md § Step 0. Then read the active mode file fully and run the spine end to end.
The shared spine (refs/protocol-core.md)
- Step 1 — Input validation. The PRD/exec-table source (mode flag +
prd-path+rows+agent) or thereport=<path>alternate.--reviewskips Steps 1–4. - Step 2 — Pre-flight, one pass. Injected scoped excerpts on an orchestrated run; otherwise the PRD (the digest on
--build), devkit and the row-relevant code. Row ownership is checked byscript-prd-digest.py --verify-rows. - Step 3 — Summary gate (
--planonly).--buildasks no opening question; a manual build asks one question at the end, "Commit?". - Step 4 — Coding standards (
--buildonly). An injected payload wins; elsescript-eng-cook-flags.py+ the standards cache, then/cookon a miss. - Step 5 — Run the mode's work, then the closing message (
../shared/refs/closing-message.md). - Step 6 — Scope enforcement, continuous. Only the assigned rows.
References
refs/plan/protocol.md—--plan: summary, output contract, the## Todos — <Agent>ticket spec, the closing shape check.refs/plan/template-todo.md— the ticket schema the build reads.refs/plan/template-eng-plan.md— the plan section shapes.refs/plan/fix-plan.md— planning fixes from areport.refs/build/protocol.md— the manual build's solo-only steps (branch, ticket check, standards, progress messages, "Commit?", sub-branch PR, summary and run report).refs/build/protocol-packet.md— the build loop, written once: tickets, TDD, full-suite gate, review and re-test, db-touch pause, one commit per ticket, output.refs/build/protocol-build-debug.md— debug mode.refs/build/fix-build.md— thereportsource.refs/build/fix-build-orchestrated.md— the fix coordinator.refs/build/bug-report.md—--bug: a bug found by hand becomes a newreport-prd-<N>-<K>pair, then the normal fix flow.refs/review/protocol.md—--review: change set, adversarial charter, severity, return contract, artifact, spawn rules. One review, whole change, by an agent that did not write the code..claude/scripts/—script-eng-db-touch.sh(production/data guardrail over this run's changes; a trip pauses for sign-off) ·script-eng-cook-flags.py(the/cookflag set from the stack) ·script-eng-comment-scan.sh(A4 comment presence) ·script-eng-commit-cap.sh(A5 commit size, advisory; a missingOversize-reason:trailer exits 3) ·script-eng-plan-shape.py(the--planclosing check) ·script-project-findings.py(the one finding→issue-ticket projection + issues-file validator) ·script-eng-fix-grade.py(fix complexity + tier→model) ·script-eng-close-loop.py(the only write to an issues file) ·script-eng-bug-report.py(writes a hand-found bug as a new report pair)../shared/refs/status-heartbeat.md— the progress-message contract- Contract: the
## Engineering — <Agent>and## Todos — <Agent>headings written by--planare howplan-emdetects a finished section and how--buildfinds its tickets. Do not rename them.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |