[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DH346WJGJFGSCC2K5BQ7WT":3,"skill-same:01M7DH346WJGJFGSCC2K5BQ7WT":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7DH346WJGJFGSCC2K5BQ7WT","pm-sync-core",null,"The canonical product-sync mechanism — stage, draft and file a product change for maintainer approval, and the lifecycle sync that moves one spec's backlog cards to specced, implementing or shipped with a decision entry","turbokast\u002Fmythhelm","turbokast","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F335585049?v=4","01M7DGYYSHNA1BW1Y9GJFN6DVC","TurboKast","01M7DGYYT6GTPCFADDKS5ZXM1Y",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpm-sync-core\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pm-sync-core\ndescription: The canonical product-sync mechanism — stage, draft and file a product change for maintainer approval, and the lifecycle sync that moves one spec's backlog cards to specced, implementing or shipped with a decision entry\nargument-hint: \"\u003Cspec-name> --to specced|implementing|shipped [--premise \\\"\u003Cverdict line>\\\"]\"\n---\n\n# PM Sync Core\n\nTwo things live here, and every product skill uses the first:\n\n- **§File a change**: how any change to `product\u002F` is drafted, validated and filed for a maintainer's approval. It is the single place that procedure is written down.\n- **§Lifecycle sync**: the mechanical status transition for one spec's cards when the spec lifecycle moves: `\u002Fcreate-spec` and `\u002Fspec` sync to `specced`, `run-spec` to `implementing`, `finalize-spec` to `shipped`.\n\nAgents never write `product\u002F` directly. `.claude\u002Fhooks\u002Fguard-product-write.sh` releases a write only against a maintainer's signed approval of that exact change (`product\u002FREADME.md`, `.claude\u002Frules\u002Fproduct-management.md`).\n\n## Input\n\n`$ARGUMENTS` for the lifecycle sync: the spec name, `--to \u003Cstatus>`, and for `specced` an optional `--premise \"\u003Cline>\"` recording the grounding verdicts on the card. Other skills call §File a change with their own drafts.\n\n## Invocation contexts\n\n- **Slash command**: runs the sync, files the requests and prints the maintainer's approve commands.\n- **Model-invoked**: the same; a calling skill's run continues after the requests are filed.\n- **Non-interactive**: the same. Filing a request writes only to `orchestration\u002Frequests\u002F`, never to `product\u002F`, so it needs no pre-approval; the product write waits for the maintainer's signature in every context. A step that needs a decision the algorithm does not encode is an escalation: stop and report it.\n\n## File a change\n\n1. **Stage.** `STAGE=\"$(mktemp -d)\"; python3 scripts\u002Fpm\u002Fpm.py stage \"$STAGE\"`. This copies the product files, including the README; nothing under `product\u002F` changes. Use a fresh directory: any existing destination file or link is rejected before copying.\n2. **Draft.** Run each `pm.py` write verb against the stage: `python3 scripts\u002Fpm\u002Fpm.py --product-dir \"$STAGE\" \u003Cverb> ... --out \"$STAGE\u002F\u003Cfile>\"`. Chain as many as the change needs; each reads the staged files and writes one back. For reviewed prose use `draft-text objectives|readme|backlog-preamble --from \u003Cscratch-source> --out \u003Cstaged-file>`; it never writes product files or changes card\u002Flog records. A new card or entry id comes from the verb itself, which reserves it with `pm.py next-id` at this moment; never type an id you remember, and never put a number in a draft you show before this step.\n3. **Record the decision.** Every change except a pure roadmap redraft appends a `decisions.md` entry with `pm.py ... decide --type \u003Ctype>`, naming the cards and the evidence.\n4. **Redraft the roadmap** when a card's status or score changed: `pm.py --product-dir \"$STAGE\" roadmap --out \"$STAGE\u002Froadmap.md\"`.\n5. **Validate** the whole staged set: `python3 scripts\u002Fpm\u002Fpm.py --product-dir \"$STAGE\" validate` must print `product: OK` (a stale-roadmap warning means step 4 was skipped). The verbs refuse a draft that would not validate, so a failure here is a finding to fix, not to file.\n6. **Check the diff is proportional**: `diff -u product\u002F\u003Cfile> \"$STAGE\u002F\u003Cfile>\"` for each file. A status flip is a few lines; if unrelated cards moved or changed, stop and find out why before filing.\n7. **File one request per changed file**, ids `\u003Cslug>-\u003Cfile stem>`:\n   `python3 scripts\u002Forchestration\u002Fapprovals.py request \u003Cslug>-backlog --path product\u002Fbacklog.md --proposed \"$STAGE\u002Fbacklog.md\" --summary \"\u003Cwhat and why>\"`.\n   Exception, a lifecycle sync under the maintainer's autonomy grant: when `python3 scripts\u002Forchestration\u002Fautonomy.py pm-sync-check --path product\u002F\u003Cfile> --proposed \"$STAGE\u002F\u003Cfile>\"` prints `pre-approved`, write that file with the Write tool instead of filing it (backlog first, then decisions, then roadmap, since the roadmap check regenerates from the written backlog), and skip step 8 for it. `guard-product-write.sh` releases exactly those writes and records them. A file it refuses is filed as above.\n8. **Hand off.** Report the request ids and the maintainer's commands: `scripts\u002Forchestration\u002Fapprove.sh show \u003Cid>`, then `approve \u003Cid> --apply` (writes the file) or `reject \u003Cid>`. Continue with independent work; never wait by polling.\n9. **Apply, if asked.** When the maintainer approved without `--apply`, write each file with the Write tool using exactly the content of `orchestration\u002Frequests\u002F\u003Cid>\u002Fproposed` in the main checkout. A block saying the approval is stale means the file changed since the request: restage and refile from step 1; never adapt the old draft by hand.\n10. **Commit** the applied files by name (`git commit -s -m \"\u003Cmsg>\" -- product\u002F\u003Cfile> ...`) on a branch, and open or update a pull request.\n\n## Lifecycle sync\n\nZero-judgment bookkeeping. A dispatcher may hand it to `harness-clerk`, passing no `effort` parameter (`knowledge\u002Fagent-routing.md`).\n\n1. **Resolve the spec** with `scripts\u002Fharness\u002Fspec-lifecycle.sh resolve \u003Cspec-name>`.\n2. **Find its cards**, as a set: every `- **Backlog card**: MH-\u003Cn>` line in the spec's `requirements.md` (or in `plan.md` for an epic), plus every card whose Spec field names the spec (`python3 scripts\u002Fpm\u002Fpm.py list --json` and read the `spec` field). No card: report `PM sync: skipped (no card names \u003Cspec-name>)` and stop. Never invent a link.\n3. **Skip what is already there**, per card: `specced` skips a card already `specced`, `implementing` or `shipped`; `implementing` skips `implementing` or `shipped`; `shipped` skips `shipped`. A `dropped` card is an escalation: a spec is moving for work the backlog says will not be done.\n4. **Stage** (§File a change step 1) and, for each remaining card, draft in the stage:\n   - `specced`: `set-status MH-\u003Cn> specced --spec \u003Cspec-name>` (the Spec field keeps any other specs it names; pass them all, comma-separated). With `--premise`, also `set MH-\u003Cn> premise-grounded \"\u003Cline>\"`.\n   - `implementing`: `set-status MH-\u003Cn> implementing`.\n   - `shipped`: `set-status MH-\u003Cn> shipped`. When the card names another spec that is not yet in `done\u002F` or `archived\u002F`, pm.py refuses and exits 1. Then the card stays `implementing`: draft `set MH-\u003Cn> half-shipped \"\u003Cspec-name> shipped in \u003CPR link>; the card ships with \u003Cremaining specs>\"` instead and report it as held.\n5. **Decision entries**, one per changed card: `decide --type lifecycle-sync --title \"MH-\u003Cn> → \u003Cstatus> (\u003Cspec-name>)\" --decision \"\u003Ccard> moved to \u003Cstatus>\" --rationale \"\u003Cspec-name> reached \u003Cspec state>\" --cards MH-\u003Cn>` with `--evidence` naming the pull request or CI run when there is one.\n6. **Roadmap, validate, file and hand off**: §File a change steps 4 to 8, request slug `sync-\u003Cspec-name>-\u003Cstatus>`.\n7. **Report**, one line per card found in step 2, so the count can be checked against the set: `PM sync: MH-\u003Cn> → \u003Cstatus> (requests \u003Cids>)`, `PM sync: MH-\u003Cn> skipped (already \u003Cstatus>)` or `PM sync: MH-\u003Cn> held at implementing (half shipped; waits for \u003Cspecs>)`. After a `shipped` sync, add: `Consider \u002Fimpact-review once the change has been in use.`\n\n## Output\n\n```text\nPM sync: \u003Cone line per card>\nRequests: \u003Cids>, for the maintainer: scripts\u002Forchestration\u002Fapprove.sh show \u003Cid> && scripts\u002Forchestration\u002Fapprove.sh approve \u003Cid> --apply\n```\n","# PM Sync Core\n\nTwo things live here, and every product skill uses the first:\n\n- **§File a change**: how any change to `product\u002F` is drafted, validated and filed for a maintainer's approval. It is the single place that procedure is written down.\n- **§Lifecycle sync**: the mechanical status transition for one spec's cards when the spec lifecycle moves: `\u002Fcreate-spec` and `\u002Fspec` sync to `specced`, `run-spec` to `implementing`, `finalize-spec` to `shipped`.\n\nAgents never write `product\u002F` directly. `.claude\u002Fhooks\u002Fguard-product-write.sh` releases a write only against a maintainer's signed approval of that exact change (`product\u002FREADME.md`, `.claude\u002Frules\u002Fproduct-management.md`).\n\n## Input\n\n`$ARGUMENTS` for the lifecycle sync: the spec name, `--to \u003Cstatus>`, and for `specced` an optional `--premise \"\u003Cline>\"` recording the grounding verdicts on the card. Other skills call §File a change with their own drafts.\n\n## Invocation contexts\n\n- **Slash command**: runs the sync, files the requests and prints the maintainer's approve commands.\n- **Model-invoked**: the same; a calling skill's run continues after the requests are filed.\n- **Non-interactive**: the same. Filing a request writes only to `orchestration\u002Frequests\u002F`, never to `product\u002F`, so it needs no pre-approval; the product write waits for the maintainer's signature in every context. A step that needs a decision the algorithm does not encode is an escalation: stop and report it.\n\n## File a change\n\n1. **Stage.** `STAGE=\"$(mktemp -d)\"; python3 scripts\u002Fpm\u002Fpm.py stage \"$STAGE\"`. This copies the product files, including the README; nothing under `product\u002F` changes. Use a fresh directory: any existing destination file or link is rejected before copying.\n2. **Draft.** Run each `pm.py` write verb against the stage: `python3 scripts\u002Fpm\u002Fpm.py --product-dir \"$STAGE\" \u003Cverb> ... --out \"$STAGE\u002F\u003Cfile>\"`. Chain as many as the change needs; each reads the staged files and writes one back. For reviewed prose use `draft-text objectives|readme|backlog-preamble --from \u003Cscratch-source> --out \u003Cstaged-file>`; it never writes product files or changes card\u002Flog records. A new card or entry id comes from the verb itself, which reserves it with `pm.py next-id` at this moment; never type an id you remember, and never put a number in a draft you show before this step.\n3. **Record the decision.** Every change except a pure roadmap redraft appends a `decisions.md` entry with `pm.py ... decide --type \u003Ctype>`, naming the cards and the evidence.\n4. **Redraft the roadmap** when a card's status or score changed: `pm.py --product-dir \"$STAGE\" roadmap --out \"$STAGE\u002Froadmap.md\"`.\n5. **Validate** the whole staged set: `python3 scripts\u002Fpm\u002Fpm.py --product-dir \"$STAGE\" validate` must print `product: OK` (a stale-roadmap warning means step 4 was skipped). The verbs refuse a draft that would not validate, so a failure here is a finding to fix, not to file.\n6. **Check the diff is proportional**: `diff -u product\u002F\u003Cfile> \"$STAGE\u002F\u003Cfile>\"` for each file. A status flip is a few lines; if unrelated cards moved or changed, stop and find out why before filing.\n7. **File one request per changed file**, ids `\u003Cslug>-\u003Cfile stem>`:\n   `python3 scripts\u002Forchestration\u002Fapprovals.py request \u003Cslug>-backlog --path product\u002Fbacklog.md --proposed \"$STAGE\u002Fbacklog.md\" --summary \"\u003Cwhat and why>\"`.\n   Exception, a lifecycle sync under the maintainer's autonomy grant: when `python3 scripts\u002Forchestration\u002Fautonomy.py pm-sync-check --path product\u002F\u003Cfile> --proposed \"$STAGE\u002F\u003Cfile>\"` prints `pre-approved`, write that file with the Write tool instead of filing it (backlog first, then decisions, then roadmap, since the roadmap check regenerates from the written backlog), and skip step 8 for it. `guard-product-write.sh` releases exactly those writes and records them. A file it refuses is filed as above.\n8. **Hand off.** Report the request ids and the maintainer's commands: `scripts\u002Forchestration\u002Fapprove.sh show \u003Cid>`, then `approve \u003Cid> --apply` (writes the file) or `reject \u003Cid>`. Continue with independent work; never wait by polling.\n9. **Apply, if asked.** When the maintainer approved without `--apply`, write each file with the Write tool using exactly the content of `orchestration\u002Frequests\u002F\u003Cid>\u002Fproposed` in the main checkout. A block saying the approval is stale means the file changed since the request: restage and refile from step 1; never adapt the old draft by hand.\n10. **Commit** the applied files by name (`git commit -s -m \"\u003Cmsg>\" -- product\u002F\u003Cfile> ...`) on a branch, and open or update a pull request.\n\n## Lifecycle sync\n\nZero-judgment bookkeeping. A dispatcher may hand it to `harness-clerk`, passing no `effort` parameter (`knowledge\u002Fagent-routing.md`).\n\n1. **Resolve the spec** with `scripts\u002Fharness\u002Fspec-lifecycle.sh resolve \u003Cspec-name>`.\n2. **Find its cards**, as a set: every `- **Backlog card**: MH-\u003Cn>` line in the spec's `requirements.md` (or in `plan.md` for an epic), plus every card whose Spec field names the spec (`python3 scripts\u002Fpm\u002Fpm.py list --json` and read the `spec` field). No card: report `PM sync: skipped (no card names \u003Cspec-name>)` and stop. Never invent a link.\n3. **Skip what is already there**, per card: `specced` skips a card already `specced`, `implementing` or `shipped`; `implementing` skips `implementing` or `shipped`; `shipped` skips `shipped`. A `dropped` card is an escalation: a spec is moving for work the backlog says will not be done.\n4. **Stage** (§File a change step 1) and, for each remaining card, draft in the stage:\n   - `specced`: `set-status MH-\u003Cn> specced --spec \u003Cspec-name>` (the Spec field keeps any other specs it names; pass them all, comma-separated). With `--premise`, also `set MH-\u003Cn> premise-grounded \"\u003Cline>\"`.\n   - `implementing`: `set-status MH-\u003Cn> implementing`.\n   - `shipped`: `set-status MH-\u003Cn> shipped`. When the card names another spec that is not yet in `done\u002F` or `archived\u002F`, pm.py refuses and exits 1. Then the card stays `implementing`: draft `set MH-\u003Cn> half-shipped \"\u003Cspec-name> shipped in \u003CPR link>; the card ships with \u003Cremaining specs>\"` instead and report it as held.\n5. **Decision entries**, one per changed card: `decide --type lifecycle-sync --title \"MH-\u003Cn> → \u003Cstatus> (\u003Cspec-name>)\" --decision \"\u003Ccard> moved to \u003Cstatus>\" --rationale \"\u003Cspec-name> reached \u003Cspec state>\" --cards MH-\u003Cn>` with `--evidence` naming the pull request or CI run when there is one.\n6. **Roadmap, validate, file and hand off**: §File a change steps 4 to 8, request slug `sync-\u003Cspec-name>-\u003Cstatus>`.\n7. **Report**, one line per card found in step 2, so the count can be checked against the set: `PM sync: MH-\u003Cn> → \u003Cstatus> (requests \u003Cids>)`, `PM sync: MH-\u003Cn> skipped (already \u003Cstatus>)` or `PM sync: MH-\u003Cn> held at implementing (half shipped; waits for \u003Cspecs>)`. After a `shipped` sync, add: `Consider \u002Fimpact-review once the change has been in use.`\n\n## Output\n\n```text\nPM sync: \u003Cone line per card>\nRequests: \u003Cids>, for the maintainer: scripts\u002Forchestration\u002Fapprove.sh show \u003Cid> && scripts\u002Forchestration\u002Fapprove.sh approve \u003Cid> --apply\n```\n",{"name":5,"description":7,"argument-hint":24},"\u003Cspec-name> --to specced|implementing|shipped [--premise \"\u003Cverdict line>\"]","main","6e250ec86158119da148ddc017b960ed3b2bee2b",".claude\u002Fskills\u002Fpm-sync-core",1,"https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm","https:\u002F\u002Fgithub.com\u002Fturbokast","https:\u002F\u002Fturbokast.com","2026-11-10 17:37:03",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add turbokast\u002Fmythhelm --skill pm-sync-core",{"tool":39,"command":40},"bunx","bunx skills add turbokast\u002Fmythhelm --skill pm-sync-core",{"tool":42,"command":43},"pnpm","pnpm dlx skills add turbokast\u002Fmythhelm --skill pm-sync-core","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpm-sync-core\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7DH77QH78C95S7A5V1GFKKF","mythhelm-deliver-backlog","Coordinate a MYTHHELM backlog run with the shared stage checks and maintainer checkpoints.","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.grok\u002Fskills\u002Fmythhelm-deliver-backlog\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7DH748EXYG9RVBWPBJ73M27","mythhelm-bootstrap","Orient a Grok Build session in the MYTHHELM repository before task or spec work.","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.grok\u002Fskills\u002Fmythhelm-bootstrap\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DH70XJE0DZA4T5DYR1TWKZ","vendor-consult","Run one advisory stage consult (premise-ground, spec-validate, task-review, change-review, stuck-oracle, dossier) with an optional external vendor, then adjudicate the answer at its anchors","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvendor-consult\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DH6X9HSQ308P5FNDSKYR5R","update-docs","Bring README, docs\u002F, knowledge\u002F, WORKFLOW.md and CLAUDE.md in line with what a shipped spec or a merged change actually did — find every statement the change made stale, fix it where readers look, and add only the new facts they need","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fupdate-docs\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DH6T82XR40XQFNRTN4AHGN","triage","Score an idea or a GitHub issue against the master spec's stages, gates and commitments, check it for duplicates, and recommend whether it becomes a backlog card; read-only","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DH6Q17PM4ESX978QYFV6H6","test-driven-development","Red-green-refactor for Go — use when implementing any feature, bug fix or behaviour change, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[]]