run
/run
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".
- Author
- swingerman ↗
- Repository
- engineer ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Original author description
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".
How it works
- When to use
- Workflow
- Handoff
- References
SKILL.md preview
---
name: run
description: 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".
---
# 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.
## Handoff
The coordinator writes **no checkpoint handoffs**: each node writes its own.
At the close (or when a stop rule fires), emit one handoff per
`${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md` with `skill: run`,
`checkpoint: null`, `artifacts: [features/NNN-<slug>/run-graph.yml]`, a
`findings_summary` of estimate vs actual, and `recommended_next` (the gate
waiting, or "done").
## References
- `${CLAUDE_PLUGIN_ROOT}/references/coordinator.md`: the standing instructions
- `${CLAUDE_PLUGIN_ROOT}/references/graph-shapes.md`: shape vocabulary, the loop rule, outside evidence
- `${CLAUDE_PLUGIN_ROOT}/references/handoff-dispatch.md`: "Coordinated nodes", the brief template
- `${CLAUDE_PLUGIN_ROOT}/scripts/dae_graph.py`: graph validator
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · swingerman/engineer | 90 | MIT |
| phnx-labs/agi-cli | 100 | Apache-2.0 |
| Insilico-org/plsi | 100 | MIT |
| jtsternberg/claude-plugins | 100 | MIT |
| jameskomo/config-drift-checker | 100 | Apache-2.0 |
| lucastamoios/skills | 100 | MIT |
| andriiklymiuk/corgi | 100 | MIT |
| lucastamoios/skills | 100 | MIT |
| Dinusha-Ekanayake/specsteward | 100 | MIT |
Database snapshot: 13.11.2026 · package version b1219809f342 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100feature-loop
Orchestrate the agent team to take one feature from idea to release-ready - spec-writer, architect, builder, reviewer, security-checker, feature-engineer (if ML), release-docs - with human approval gates. Use when the owner says "run the loop", "build feature X", or gives a new feature idea. - 80Coordinator
Run as the human's coordinator: the one agent that plans, dispatches Orca workers, judges their reports, keeps the board and the hand-over state, and asks the human only for sensitive decisions. Load when the user asks you to coordinate, dispatch or supervise, or when a… - 100ai-orchestrator
Build a whole feature end-to-end through subagents. It plans gated checkpoints, writes tests and prototypes, then loops each checkpoint through implement → behavior gate (CLI/code tests, UI e2e last) → UI gate (live vs prototype) → adversarial review gate until every checkpoint… - 100team-planex
Unified team skill for plan-and-execute pipeline. Pure router — coordinator always. Beat model is coordinator-only in monitor.md. Triggers on "team planex". - 100team-planex
Unified team skill for plan-and-execute pipeline. Pure router — coordinator always. Beat model is coordinator-only in monitor.md. Triggers on "team planex". - 90starter
Use when you need to act as the Project Manager orchestrating the agent swarm (Architect, Engineer, Auditor, Product Owner) to drive a feature, bug fix, or refactor through the full spec→plan→execute lifecycle. Load this role before running any operation. Triggers - "be the…