Pick and run the next harness command from the repo's state, then repeat until a person is needed. A script chooses the route. Use when the user says go, what next, which command do I use, or take this repo forward. `status` shows the ladder; `stop` sets the stop file.
Install
npx skillscat add dobeu-tech-eco/dts2-marketplace/go Install via the SkillsCat registry.
Directory edition: do not run bundled scripts or hooks, a package launcher, or a download piped into a shell. Do not read tokens or credential files from the machine. Carry out the step with Read, Edit, Grep, Glob, and git or gh, and write the files the step names.
Go: the next command, chosen from repo state
One entry point. next_step.py reads the repo and returns one rung of a fixed ladder. You run the command it names, then ask it again. You never choose the route yourself, and you never skip a rung because it looks unnecessary.
The ladder
The first rung that applies wins.
| Rung | State | Next command |
|---|---|---|
| 0 | stopped (.harness/STOP exists) |
none: a person deletes the file |
| 1 | no-composio-decision |
/dt:composio (the user types it) |
| 2 | no-end-state |
/dt:setup |
| 3 | end-state-not-approved |
/dt:setup to revise and approve |
| 4 | roadmap-not-approved |
none: the owner approves the roadmap |
| 5 | sections-outstanding |
/dt:dpp when two or more sections are todo, else /dt:run |
| 6 | open-pull-requests |
/dt:pr-sweep |
| 7 | action-items-open |
/dt:action-items |
| 8 | deploy-planned |
/dt:run for the planned deploy |
| 9 | acceptance-outstanding |
/dt:run for the unmet acceptance criteria |
| 10 | complete |
/dt:learn |
Steps
- Count open pull requests when
ghis signed in:gh pr list --state open --json number --jq length. Ifghis missing or fails, leave the count out; rung 6 is then skipped and you say so once. - Ask for the next step.
python3 -I "${CLAUDE_PLUGIN_ROOT}/scripts/next_step.py" --repo . [--open-prs <n>] next. It prints one JSON object:rung,state,next_command,reason,blocked_on. - Act on it.
blocked_onis set: printStopped at rung <rung> (<state>): <blocked_on>and stop. Do not look for another way forward.next_commandiscomposio: that skill starts only when the user types it. PrintNext: type /dt:composio. <reason>and stop.- Otherwise print
Next: /dt:<next_command>. <reason>and run that skill now. Its own checkpoints and gates apply unchanged.
- Repeat from step 1 when the command finishes. Stop when the script returns the same rung twice in a row, and report that rung as stalled with what the command left undone.
Roadmap approval (rung 4)
The roadmap is the end state's sections and acceptance criteria. Its scope key changes when a section or criterion is added, removed or renamed, and stays the same when work is completed.
- Write the view:
python3 -I "${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.py" --repo . build. Show.harness/roadmap.mdto the owner. - Show the
blocked_ontext. It carries the exact entry the owner adds to.claude/settings.local.json. - Stop. Only the owner edits that file. Never write it, and never treat a yes in chat as the approval.
A changed scope needs a new approval. Say so when rung 4 returns after the roadmap was approved before.
Other forms
/dt:go status: runnext_step.py --repo . [--open-prs <n>] statusand show the ladder as printed. The current rung is marked>. Read-only./dt:go stop <reason>: runnext_step.py --repo . stop --reason "<reason>". Every later/dt:goreturns rung 0 until a person deletes.harness/STOP. The loop guard forfullautoreads the same file. Never delete it yourself.
Any seat can start it
The router is a plain script with no model call, so every seat on the roster gets the same answer from the same repo. A seat that is not Claude (a Codex, Grok or other provider session) starts the ladder by running next_step.py --repo . next itself and following the steps above with its own way of running a harness command.
Starting the ladder gives a seat no extra authority. The owner's approvals, the hard gates and the stop file apply to every seat alike. When a rung goes to a council, the Claude seat is head of council and breaks a split, as in autopilot.
Rules
- The script reads files only. It makes no network call and changes nothing except in
stop. - Roadmap approval covers the plan. It does not approve a merge to a protected branch or a deploy. Those keep their own approval, and the merge guard and policy gate still decide.
- Tests, checks, the secret scan and
do_not_touchstay hard gates. No rung, vote or council overrides one. - If the script fails or prints something that is not the JSON above, report the output and stop. Do not guess the rung.