Use to drive one feature from CP2 to CP8 under a coordinator. It proposes the feature's agent graph (shapes, model classes, loop caps, cost estimate), then dispatches every checkpoint as a fresh agent, stopping only at the front and back human gates. Triggers — "/engineer.run <feature>", "run this feature end to end", "drive the feature", "coordinate the pipeline", "build it through to verify".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# run
One coordinator per feature, CP2 → CP8. The coordinator is the graph's one
model-decided node: it **chooses** the graph (shapes, model class per node, loop
caps), records the choice, and then follows fixed edges. Each checkpoint runs as
a fresh agent, and the coordinator never reads source code.
Your standing instructions are `${CLAUDE_PLUGIN_ROOT}/references/coordinator.md`.
Read it in full before step 1. This file is only the entry point.
## When to use
- A Ready feature (CP1.5) that you want driven through the pipeline with only
the front and back gates as human stops.
- A half-done feature: the run resumes from the latest complete checkpoint.
**Not for:**
- Several features at once. Use Decarchy, one coordinator per worktree.
- A single checkpoint. Call that skill directly; every skill still works
standalone, exactly as before.
- An XS feature. The run branches to `/engineer.express` at entry.
## Workflow
Execute `coordinator.md` from "The run". In short: resolve the feature (XS goes
to `/engineer.express`), propose a graph that `dae_graph.py` accepts, run its
segments, stop only at the gates, and compare the actual run with the proposal
at the close.
…
The line at the top of this page pins the label git:20261020.a98004e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_ordrtwsvt3vzffwt
GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/run
GET https://markdownregistry.com/api/v1/blob/559a744365568f1d558663af98f4e9b8c9c465bf0e2bdeceed73df76332ebf78
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
swingerman/engineer · crap-analyzer/skills/crap-analyzer/SKILL.md · Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP…
swingerman/engineer · engineer/skills/arch-check/SKILL.md · Use to check a feature's code against the charter's architecture rules — dependency layering, cycles, forbidden…
swingerman/engineer · engineer/skills/atdd/SKILL.md · Use to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline. The…
swingerman/engineer · engineer/skills/clarify/SKILL.md · Use when a single DAE artifact has ambiguities to resolve. Triggers — "/engineer.clarify", "clarify this spec"…
swingerman/engineer · engineer/skills/consistency-check/SKILL.md · Use to validate DAE artifacts for schema correctness and cross-artifact consistency. Triggers —…
swingerman/engineer · engineer/skills/discover-acs/SKILL.md · Use when a Ready feature needs its acceptance criteria discovered before specs are written. Triggers —…
swingerman/engineer · engineer/skills/discuss/SKILL.md · Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "/engineer.discuss"…
swingerman/engineer · engineer/skills/express/SKILL.md · Use to build an XS (express-lane) feature in one pass — intake→implement→verify in a single context, no handoff chain…
swingerman/engineer · engineer/skills/feature-edit/SKILL.md · Use when an in-flight feature must change — scope shifts, an AC is refined, the plan evolves, a behavior is added or…
swingerman/engineer · engineer/skills/feature-init/SKILL.md · Use when a new feature folder must be created for the DAE pipeline, or when discuss promotes/parks an idea. Triggers —…
swingerman/engineer · engineer/skills/fix/SKILL.md · Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers —…
swingerman/engineer · engineer/skills/harden/SKILL.md · Use after a feature passes Light Verify (CP7), to prove the tests actually catch bugs and, where the code warrants it…
rustyrazorblade/skills · plugins/easy-db-lab/skills/run/SKILL.md · Executes a plan step by step in an explicit cluster workspace, confirming each step with the user, journaling as work…
chainlesschain/chainlesschain · packages/cli/src/skills-bundled/run/SKILL.md · Launch and drive this project's app to see a change actually working — not just passing tests. Use when asked to run…
dmitriyyukhanov/agent-plugins · plugins/issue-to-pr/skills/run/SKILL.md · Drive a GitHub issue — bare or tracked on a Project board — from triage to a merge-ready PR through a gated pipeline…
dmitriyyukhanov/claude-plugins · plugins/issue-to-pr/skills/run/SKILL.md · Drive a GitHub issue — bare or tracked on a Project board — from triage to a merge-ready PR through a gated pipeline…
