running-the-omniplatform-program
Use when leading or continuing the Godot-on-Polaris-Key execution program (docs/research/2026-09-29-godot-omniplatform/program/) - choosing ready work packages, dispatching the pkey-* role agents, routing plan-mode work through approval, reviewing, updating statuses and escalating to the human.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- running-the-omniplatform-program
- description
- Use when leading or continuing the Godot-on-Polaris-Key execution program (docs/research/2026-09-29-godot-omniplatform/program/) - choosing ready work packages, dispatching the pkey-* role agents, routing plan-mode work through approval, reviewing, updating statuses and escalating to the human.
03 SKILL.md 正文
Running the omniplatform program
The program lives in docs/research/2026-09-29-godot-omniplatform/program/. Its README.md is the operating manual; this skill is the lead's checklist. You are the lead: you dispatch and integrate, and the role agents in .claude/agents/pkey-*.md do the work.
Each session
- [ ] Read
AGENTS.md,CLAUDE.mdandprogram/README.md(§3 the loop, §5 hotspots, §6 human inputs). - [ ] Pull the default branch. Run
node program/check.mjsand fix any graph error first. - [ ] Review what is in flight:
node program/check.mjs --summary, and the openwp/*branches and PRs. - [ ] For each
awaiting-approvalplan, ask the human for a decision. Do not implement unapproved plans.
Dispatching
-
[ ] Run
node program/check.mjs --ready. Take from the top, respecting the §5 hotspot rules:- one corpus-touching package at a time;
- protocol changes only inside approved plans;
- builders leave migrations as
00XX_<name>.sql; the lead numbers them at merge.
-
[ ] Skip ✋ packages whose human inputs are missing. Ask for those inputs in one message, grouped by provider.
-
[ ] Send ⚑ (plan-mode) packages to
pkey-wire-plannerfirst. -
[ ] Start every other package with the role named in
workpackages.json. Give the agent:- the work-package id;
- the brief path;
- the branch name
wp/<ID>-<slug>; - any human inputs received.
Independent packages run in parallel, and one message can start several agents.
-
[ ]
D-*packages run invladzaharia/diceroll, which must be attached to the session first.
When an agent reports
- [ ] Start
pkey-wp-revieweron the branch. Send blocking findings back to the same role agent for one fix round. If re-review still blocks, take the branch back rather than starting another loop. - [ ] Check that the PR body carries the brief's acceptance checklist, and that the status is
in-reviewinworkpackages.json. - [ ] When the reviewer passes it, add the PR's last commit: the brief's hand-off line
check.mjs --set <ID> done, then prettier onworkpackages.jsonandINDEX.md. Hand the PR to the human to merge. After the merge:- confirm the status reads
doneon the default branch; - re-run
--ready; - update any downstream brief whose named interface changed.
- confirm the status reads
- [ ] Record deviations the agent reported. A scope or estimate change of more than half goes to the human before more work is dispatched on that line.
Integrating and closing agents
- [ ] Register each launched workflow or agent in
$PKEY_LEAD/active.$PKEY_LEADis the lead directory set in the owner's shell profile. - [ ] Merge a passed branch locally with
$PKEY_LEAD/merge.sh. It auto-resolves only generated files and stops on any other conflict. Send real conflicts to one integration agent for the batch, not back to each builder. - [ ] Run
$PKEY_LEAD/gate.sh(a wrapper overpnpm gate) once per integration batch. CI onmainruns the full matrix, and a deploy waits for it. - [ ] Run
$PKEY_LEAD/stall-watch.shin the background whenever agents run. Act on every quiet, long or unclosed report; resume, stop or re-scope the work, then re-arm the watcher. - [ ] Once a hand-back is merged, re-dispatched or filed, stop the agent with
TaskStopand remove it from$PKEY_LEAD/active, unless it is sending that agent more work. After a batch of hand-backs, runListAgentsand stop every entry shown ascompleted.
Escalate to the human, and pause the affected line, when
- a hard rule in
AGENTS.mdwould have to bend; - a plan needs a decision the research left open;
- a human-held input is missing (accounts, keys, devices, deploys, the P0-08 production deploy before any new service slug);
- two briefs contradict each other, or the code contradicts a brief in a way that changes scope.
When the graph changes
- [ ] Edit
workpackages.jsonand the briefs, then runcheck.mjs --sync-briefs, then--write-index, then prettier, thencheck.mjs(program README §8). - [ ] Turn items from the README's "Known gaps without a work package" into packages when their phase approaches.
Never
- Merge PRs, deploy, create cloud resources or store credentials on the human's behalf, unless the human has explicitly delegated that.
- Hand-edit
INDEX.md, the corpus or generated docs. - Renumber a work package that has started.
04 同仓库更多 Skills
r7-secret
Sets a secret outside a handoff fence. Use when testing rule 7.
r6-gated-link
Links an admin page. Use when testing rule 6.
r5-programme-id
Names a programme id. Use when testing rule 5.
r4-names
Cites names that do not exist. Use when testing rule 4.
r3-deep
A reference nests a directory. Use when testing rule 3.
Bad_Name
The name breaks the pattern. Use when testing rule 1.