[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KXB49ECPBTR46NZ71MBWR":3,"skill-same:01M77KXB49ECPBTR46NZ71MBWR":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M77KXB49ECPBTR46NZ71MBWR","running-the-omniplatform-program",null,"Use when leading or continuing the Godot-on-Polaris-Key execution program (docs\u002Fresearch\u002F2026-09-29-godot-omniplatform\u002Fprogram\u002F) - choosing ready work packages, dispatching the pkey-* role agents, routing plan-mode work through approval, reviewing, updating statuses and escalating to the human.","vladzaharia\u002Fpolaris-key","vladzaharia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F79390?v=4","01M77KX2HEVKT2TK6WQ2V7WEGG","Vlad Zaharia","01M77KX2J6W3MV6A5N08VTS8AR",0,"MIT","https:\u002F\u002Fgithub.com\u002Fvladzaharia\u002Fpolaris-key\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunning-the-omniplatform-program\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: running-the-omniplatform-program\ndescription: Use when leading or continuing the Godot-on-Polaris-Key execution program (docs\u002Fresearch\u002F2026-09-29-godot-omniplatform\u002Fprogram\u002F) - choosing ready work packages, dispatching the pkey-* role agents, routing plan-mode work through approval, reviewing, updating statuses and escalating to the human.\n---\n\n# Running the omniplatform program\n\nThe program lives in `docs\u002Fresearch\u002F2026-09-29-godot-omniplatform\u002Fprogram\u002F`. 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\u002Fagents\u002Fpkey-*.md` do the work.\n\n## Each session\n\n- [ ] Read `AGENTS.md`, `CLAUDE.md` and `program\u002FREADME.md` (§3 the loop, §5 hotspots, §6 human inputs).\n- [ ] Pull the default branch. Run `node program\u002Fcheck.mjs` and fix any graph error first.\n- [ ] Review what is in flight: `node program\u002Fcheck.mjs --summary`, and the open `wp\u002F*` branches and PRs.\n- [ ] For each `awaiting-approval` plan, ask the human for a decision. Do not implement unapproved plans.\n\n## Dispatching\n\n- [ ] Run `node program\u002Fcheck.mjs --ready`. Take from the top, respecting the §5 hotspot rules:\n  - one corpus-touching package at a time;\n  - protocol changes only inside approved plans;\n  - builders leave migrations as `00XX_\u003Cname>.sql`; the lead numbers them at merge.\n- [ ] Skip ✋ packages whose human inputs are missing. Ask for those inputs in one message, grouped by provider.\n- [ ] Send ⚑ (plan-mode) packages to `pkey-wire-planner` first.\n- [ ] Start every other package with the role named in `workpackages.json`. Give the agent:\n  - the work-package id;\n  - the brief path;\n  - the branch name `wp\u002F\u003CID>-\u003Cslug>`;\n  - any human inputs received.\n\n  Independent packages run in parallel, and one message can start several agents.\n\n- [ ] `D-*` packages run in `vladzaharia\u002Fdiceroll`, which must be attached to the session first.\n\n## When an agent reports\n\n- [ ] Start `pkey-wp-reviewer` on 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.\n- [ ] Check that the PR body carries the brief's acceptance checklist, and that the status is `in-review` in `workpackages.json`.\n- [ ] When the reviewer passes it, add the PR's last commit: the brief's hand-off line `check.mjs --set \u003CID> done`, then prettier on `workpackages.json` and `INDEX.md`. Hand the PR to the human to merge. After the merge:\n  - confirm the status reads `done` on the default branch;\n  - re-run `--ready`;\n  - update any downstream brief whose named interface changed.\n- [ ] 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.\n\n## Integrating and closing agents\n\n- [ ] Register each launched workflow or agent in `$PKEY_LEAD\u002Factive`. `$PKEY_LEAD` is the lead\n      directory set in the owner's shell profile.\n- [ ] Merge a passed branch locally with `$PKEY_LEAD\u002Fmerge.sh`. It auto-resolves only generated\n      files and stops on any other conflict. Send real conflicts to **one integration agent** for the\n      batch, not back to each builder.\n- [ ] Run `$PKEY_LEAD\u002Fgate.sh` (a wrapper over `pnpm gate`) once per integration batch. CI on `main` runs the full matrix, and\n      a deploy waits for it.\n- [ ] Run `$PKEY_LEAD\u002Fstall-watch.sh` in the background whenever agents run. Act on every quiet,\n      long or unclosed report; resume, stop or re-scope the work, then re-arm the watcher.\n- [ ] Once a hand-back is merged, re-dispatched or filed, stop the agent with `TaskStop` and remove\n      it from `$PKEY_LEAD\u002Factive`, unless it is sending that agent more work. After a batch of\n      hand-backs, run `ListAgents` and stop every entry shown as `completed`.\n\n## Escalate to the human, and pause the affected line, when\n\n- a hard rule in `AGENTS.md` would have to bend;\n- a plan needs a decision the research left open;\n- a human-held input is missing (accounts, keys, devices, deploys, the P0-08 production deploy before any new service slug);\n- two briefs contradict each other, or the code contradicts a brief in a way that changes scope.\n\n## When the graph changes\n\n- [ ] Edit `workpackages.json` and the briefs, then run `check.mjs --sync-briefs`, then `--write-index`, then prettier, then `check.mjs` (program README §8).\n- [ ] Turn items from the README's \"Known gaps without a work package\" into packages when their phase approaches.\n\n## Never\n\n- Merge PRs, deploy, create cloud resources or store credentials on the human's behalf, unless the human has explicitly delegated that.\n- Hand-edit `INDEX.md`, the corpus or generated docs.\n- Renumber a work package that has started.\n","# Running the omniplatform program\n\nThe program lives in `docs\u002Fresearch\u002F2026-09-29-godot-omniplatform\u002Fprogram\u002F`. 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\u002Fagents\u002Fpkey-*.md` do the work.\n\n## Each session\n\n- [ ] Read `AGENTS.md`, `CLAUDE.md` and `program\u002FREADME.md` (§3 the loop, §5 hotspots, §6 human inputs).\n- [ ] Pull the default branch. Run `node program\u002Fcheck.mjs` and fix any graph error first.\n- [ ] Review what is in flight: `node program\u002Fcheck.mjs --summary`, and the open `wp\u002F*` branches and PRs.\n- [ ] For each `awaiting-approval` plan, ask the human for a decision. Do not implement unapproved plans.\n\n## Dispatching\n\n- [ ] Run `node program\u002Fcheck.mjs --ready`. Take from the top, respecting the §5 hotspot rules:\n  - one corpus-touching package at a time;\n  - protocol changes only inside approved plans;\n  - builders leave migrations as `00XX_\u003Cname>.sql`; the lead numbers them at merge.\n- [ ] Skip ✋ packages whose human inputs are missing. Ask for those inputs in one message, grouped by provider.\n- [ ] Send ⚑ (plan-mode) packages to `pkey-wire-planner` first.\n- [ ] Start every other package with the role named in `workpackages.json`. Give the agent:\n  - the work-package id;\n  - the brief path;\n  - the branch name `wp\u002F\u003CID>-\u003Cslug>`;\n  - any human inputs received.\n\n  Independent packages run in parallel, and one message can start several agents.\n\n- [ ] `D-*` packages run in `vladzaharia\u002Fdiceroll`, which must be attached to the session first.\n\n## When an agent reports\n\n- [ ] Start `pkey-wp-reviewer` on 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.\n- [ ] Check that the PR body carries the brief's acceptance checklist, and that the status is `in-review` in `workpackages.json`.\n- [ ] When the reviewer passes it, add the PR's last commit: the brief's hand-off line `check.mjs --set \u003CID> done`, then prettier on `workpackages.json` and `INDEX.md`. Hand the PR to the human to merge. After the merge:\n  - confirm the status reads `done` on the default branch;\n  - re-run `--ready`;\n  - update any downstream brief whose named interface changed.\n- [ ] 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.\n\n## Integrating and closing agents\n\n- [ ] Register each launched workflow or agent in `$PKEY_LEAD\u002Factive`. `$PKEY_LEAD` is the lead\n      directory set in the owner's shell profile.\n- [ ] Merge a passed branch locally with `$PKEY_LEAD\u002Fmerge.sh`. It auto-resolves only generated\n      files and stops on any other conflict. Send real conflicts to **one integration agent** for the\n      batch, not back to each builder.\n- [ ] Run `$PKEY_LEAD\u002Fgate.sh` (a wrapper over `pnpm gate`) once per integration batch. CI on `main` runs the full matrix, and\n      a deploy waits for it.\n- [ ] Run `$PKEY_LEAD\u002Fstall-watch.sh` in the background whenever agents run. Act on every quiet,\n      long or unclosed report; resume, stop or re-scope the work, then re-arm the watcher.\n- [ ] Once a hand-back is merged, re-dispatched or filed, stop the agent with `TaskStop` and remove\n      it from `$PKEY_LEAD\u002Factive`, unless it is sending that agent more work. After a batch of\n      hand-backs, run `ListAgents` and stop every entry shown as `completed`.\n\n## Escalate to the human, and pause the affected line, when\n\n- a hard rule in `AGENTS.md` would have to bend;\n- a plan needs a decision the research left open;\n- a human-held input is missing (accounts, keys, devices, deploys, the P0-08 production deploy before any new service slug);\n- two briefs contradict each other, or the code contradicts a brief in a way that changes scope.\n\n## When the graph changes\n\n- [ ] Edit `workpackages.json` and the briefs, then run `check.mjs --sync-briefs`, then `--write-index`, then prettier, then `check.mjs` (program README §8).\n- [ ] Turn items from the README's \"Known gaps without a work package\" into packages when their phase approaches.\n\n## Never\n\n- Merge PRs, deploy, create cloud resources or store credentials on the human's behalf, unless the human has explicitly delegated that.\n- Hand-edit `INDEX.md`, the corpus or generated docs.\n- Renumber a work package that has started.\n",{"name":5,"description":7},"main","653956a45d68cd6e3669d7a8482ef154b5b8373d",".claude\u002Fskills\u002Frunning-the-omniplatform-program","https:\u002F\u002Fgithub.com\u002Fvladzaharia\u002Fpolaris-key","https:\u002F\u002Fgithub.com\u002Fvladzaharia","https:\u002F\u002Fvlad.gg","2026-11-14 10:31:35",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add vladzaharia\u002Fpolaris-key --skill running-the-omniplatform-program",{"tool":37,"command":38},"bunx","bunx skills add vladzaharia\u002Fpolaris-key --skill running-the-omniplatform-program",{"tool":40,"command":41},"pnpm","pnpm dlx skills add vladzaharia\u002Fpolaris-key --skill running-the-omniplatform-program","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvladzaharia\u002Fpolaris-key\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunning-the-omniplatform-program\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M77KYBX8FSRNXMKPRECZWM88","r7-secret","Sets a secret outside a handoff fence. Use when testing rule 7.","https:\u002F\u002Fgithub.com\u002Fvladzaharia\u002Fpolaris-key\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Fr7-secret\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77KY8JAWQKSF3VJGFVSW539","r6-gated-link","Links an admin page. Use when testing rule 6.","https:\u002F\u002Fgithub.com\u002Fvladzaharia\u002Fpolaris-key\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Fr6-gated-link\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77KY5A9SHYY73C7G1TVGCF9","r5-programme-id","Names a programme id. Use when testing rule 5.","https:\u002F\u002Fgithub.com\u002Fvladzaharia\u002Fpolaris-key\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Fr5-programme-id\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77KY2JHMYJXKETK8XR1BEN9","r4-names","Cites names that do not exist. Use when testing rule 4.","https:\u002F\u002Fgithub.com\u002Fvladzaharia\u002Fpolaris-key\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Fr4-names\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77KY17XDV8GD735M5F7TZ14","r3-deep","A reference nests a directory. Use when testing rule 3.","https:\u002F\u002Fgithub.com\u002Fvladzaharia\u002Fpolaris-key\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Fr3-deep\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77KXYNWD7YKCQV2H7AHAKEY","Bad_Name","The name breaks the pattern. Use when testing rule 1.","https:\u002F\u002Fgithub.com\u002Fvladzaharia\u002Fpolaris-key\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Fr1-name\u002FSKILL.md",[],[]]