[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DH25BMPMWD80458CVF1BSJ":3,"skill-same:01M7DH25BMPMWD80458CVF1BSJ":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},"01M7DH25BMPMWD80458CVF1BSJ","finalize-spec",null,"Close a spec whose last task has merged — verify every task and main's CI from GitHub, review the whole spec's diff, write the retrospective and proposals, land one finalize pull request that moves the spec to done with its docs and changelog, watch main's CI for it, sync the backlog, and optionally prepare a release","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\u002Ffinalize-spec\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: finalize-spec\ndescription: Close a spec whose last task has merged — verify every task and main's CI from GitHub, review the whole spec's diff, write the retrospective and proposals, land one finalize pull request that moves the spec to done with its docs and changelog, watch main's CI for it, sync the backlog, and optionally prepare a release\nargument-hint: \"\u003Cspec-name> [--alias \u003Cword>] [--release] [--publish]\"\n---\n\n# Finalize Spec\n\nIn MYTHHELM every task already lands as its own reviewed pull request, so a spec in `specs\u002Funfinalized\u002F` is code on `main`. Finalizing closes it: a review of the whole spec rather than one task at a time, a retrospective that feeds the harness's learning loop, one pull request that files the record (`specs\u002Fdone\u002F`, docs, changelog, proposals), and a check that `main` stays green afterwards.\n\nEvery verdict here comes from `scripts\u002Fharness\u002Ffinalize.py`, which reads git and GitHub; `knowledge\u002Ffinalize.md` explains what each step protects against. A sub-agent's prose is never evidence.\n\n## Input\n\n`$ARGUMENTS`: `\u003Cspec-name> [--alias \u003Cword>] [--release] [--publish]`.\n\n- `--alias`: the short name in the spec's branch names and pull-request titles; reuse the one `\u002Frun-spec` used (default: the spec name).\n- `--release`: also run `\u002Ffinalize-spec-tag` to prepare release notes. `--publish` passes on to it: the maintainer's request to publish the release (`\u002Ffinalize-spec-tag` §Publish).\n\n## Invocation contexts\n\n- **Slash command**: runs Steps 0–8. The merges of the finalize pull request and of any fix pull request are this skill's own, and invoking it is the approval for them.\n- **Model-invoked**: the same.\n- **Non-interactive**: the same, with no questions; every escalation stops the run and returns the stop report. A finalizer that is itself a subagent receives no background notifications: it waits on CI and reviews in the foreground (`finalize.py ci --wait` and `gh pr checks --watch` with a raised Bash timeout), never by ending its turn.\n\n## Sub-skills\n\n| Step | Skill | Writes |\n|---|---|---|\n| 1 | `\u002Ffinalize-spec-verify` | nothing |\n| 2 | `\u002Ffinalize-spec-review` | `## Review Summary` in the spec's `retrospective.md` |\n| 3 | `\u002Ffinalize-spec-retrospective` | the rest of `retrospective.md`; `.claude\u002Fproposals\u002Fpending.md` |\n| 4 | `\u002Ffinalize-spec-publish` (runs `\u002Ffinalize-spec-epic-rollup` and `\u002Fupdate-docs`) | the finalize pull request |\n| 5 | `\u002Ffinalize-spec-verify-ci` | fix pull requests, when main turns red |\n| 6 | `\u002Ffinalize-spec-pm` | approval requests for the backlog |\n| 7 | `\u002Ffinalize-spec-tag` (with `--release`) | nothing public unless `--publish` |\n\n## Step 0 — Worktree\n\nFinalizing never happens in the shared checkout: other sessions use its index and working tree, and a commit there can sweep their work into yours. Every later step reads and writes in the finalize worktree (`\u003Cwt>`).\n\nFirst decide from GitHub, not from memory, whether this is a resumed run: `git fetch origin`, then `gh pr list --state all --head docs\u002F\u003Calias>-finalize --json number,state,mergeCommit`.\n\n- **Merged** finalize pull request (the spec is in `specs\u002Fdone\u002F` on origin\u002Fmain): the record has landed. When the run-events log already holds this spec's `lifecycle` row `unfinalized -> done` with `result: ok` (`grep` it in the main checkout's `.claude\u002Fdata\u002Frun-events.jsonl`), the finalize is complete: report that and stop. Otherwise go straight to Step 5 with its merge commit, then Steps 6–8; `finalize-spec-verify` would rightly refuse a spec already in `done\u002F`. The log is local, so another machine re-runs Steps 5–6, which is safe: a green verdict re-verified is still green, and `pm-sync-core` skips a card already `shipped`.\n- **Open** finalize pull request: use its worktree, or recreate one from the branch (`git worktree add ..\u002F\u003Crepo>-\u003Calias>-finalize docs\u002F\u003Calias>-finalize`), and go straight to `\u002Ffinalize-spec-publish` step 7.\n- **None**, or only closed unmerged ones: a fresh run from Step 1, in a worktree that holds only this run's work:\n  - No branch `docs\u002F\u003Calias>-finalize` and no worktree at the path: `git worktree add -b docs\u002F\u003Calias>-finalize ..\u002F\u003Crepo>-\u003Calias>-finalize origin\u002Fmain`.\n  - A stopped earlier run left them: reuse that worktree. Bring it current with `git -C \u003Cwt> merge origin\u002Fmain`; the steps rewrite everything they own (the Review Summary is replaced, the retrospective's sections rewritten). A branch without a worktree is recreated with `git worktree add ..\u002F\u003Crepo>-\u003Calias>-finalize docs\u002F\u003Calias>-finalize`. Never force-remove either one: a worktree holding changes this skill does not write is an escalation.\n\nRecord the start: `python3 scripts\u002Fharness\u002Frunspec.py event --spec \u003Cspec> --kind lifecycle --detail \"finalize start\"`.\n\n## Steps\n\n1. **Verify** — `\u002Ffinalize-spec-verify \u003Cspec> --alias \u003Calias>`. Continue only on `verdict=ready`.\n2. **Review** — `\u002Ffinalize-spec-review \u003Cspec>`. When it reports open critical findings, stop: each is fixed in its own pull request (below), then `git -C \u003Cwt> merge origin\u002Fmain` and re-run from Step 1, passing the fix pull requests to `\u002Ffinalize-spec-review` as `--extra-pr`.\n3. **Retrospective** — `\u002Ffinalize-spec-retrospective \u003Cspec>`.\n4. **Publish** — `\u002Ffinalize-spec-publish \u003Cspec> --alias \u003Calias>`: move the spec to `done\u002F`, roll up its epic, update the docs and the changelog, open the finalize pull request, answer its review, merge it on `verdict=ready`, confirm it on origin\u002Fmain.\n5. **Verify CI** — `\u002Ffinalize-spec-verify-ci \u003Cspec> --sha \u003Cfinalize merge commit> --alias \u003Calias>`.\n6. **Backlog** — `\u002Ffinalize-spec-pm \u003Cspec>`. It runs after CI is green, because a card is `shipped` only when the code is merged and main is green.\n7. **Release** — with `--release` only: `\u002Ffinalize-spec-tag \u003Cspec> [--publish]`. Without it, report `Release: not requested`.\n8. **Clean up and report.** When the finalize worktree still exists: `git -C \u003Cwt> status --porcelain` prints nothing, then `git worktree remove \u003Cwt>`; when the local branch still exists, `git branch -d docs\u002F\u003Calias>-finalize`. After a squash merge `-d` refuses, because the branch's own commits never reached `main`: leave the branch and name it in the report for the maintainer, never force-delete it. Record `runspec.py event --spec \u003Cspec> --kind lifecycle --detail \"unfinalized -> done\" --result ok`, then print the report.\n\n## Fix pull requests\n\nA confirmed critical review finding (Step 2) or a real CI failure (Step 5) is fixed like a task: one pull request per fix, by the agent that owns the files (`knowledge\u002Fdomains.md`), dispatched with `subagent_type` and `isolation: \"worktree\"`, following `\u002Fimplement` Steps 3–9 but with no task entry. Title it `fix: \u003Cwhat> (\u003Calias> fix)` so `finalize.py verify` sees it while it is open. Merge it on `python3 scripts\u002Fharness\u002Ffinalize.py publish-check --spec \u003Cspec> --pr \u003Cn> --fix` printing `verdict=ready`, then confirm its merge commit on origin\u002Fmain. Print `dispatched=N returned=M failed=K` for every batch of fix dispatches.\n\n## Escalations (the run stops)\n\n1. `finalize-spec-verify` is not ready for a reason no fix pull request can remove: a task incomplete, the spec in the wrong state, the required checks changed, the gate weakened.\n2. A critical finding the fixer cannot resolve, or one that means the spec itself is wrong.\n3. Three review rounds leave the finalize pull request not ready.\n4. `\u002Ffinalize-spec-verify-ci` escalates: an `infra` or `unknown` failure, two fix cycles without green, or a wait budget spent.\n5. A guard blocked this session, or a leak reached a title, body or pushed commit.\n\nThe stop report names the step, the evidence (verbatim, at most ten lines), what is in flight, and the decision needed. The spec stays where it is on origin\u002Fmain; re-running `\u002Ffinalize-spec \u003Cspec>` resumes.\n\n## Output\n\n```text\n## Finalized: \u003Cspec>\n\nVerify:     verdict=ready (\u003Ctasks> tasks, last merge \u003Csha7>, main green)\nReview:     \u003Crange>; findings critical N \u002F important N \u002F suggestion N; open critical 0; vendor \u003Cresult>\nRetro:      specs\u002Fdone\u002F\u003Cspec>\u002Fretrospective.md; proposals \u003Cids or none>\nPublish:    PR #\u003Cn> merged as \u003Csha7>; epic \u003Crolled up | no-op>; docs \u003Cfiles or none>; changelog \u003Centries or none (reason)>\nVerify CI:  \u003Cgreen | green after fix PRs #.. | escalated: reason>\nBacklog:    \u003Cpm-sync lines | PM sync pending (reason)>\nRelease:    \u003Cnot requested | notes prepared at \u003Cpath> | published vX.Y.Z>\ndispatched=\u003CN> returned=\u003CM> failed=\u003CK>\n```\n","# Finalize Spec\n\nIn MYTHHELM every task already lands as its own reviewed pull request, so a spec in `specs\u002Funfinalized\u002F` is code on `main`. Finalizing closes it: a review of the whole spec rather than one task at a time, a retrospective that feeds the harness's learning loop, one pull request that files the record (`specs\u002Fdone\u002F`, docs, changelog, proposals), and a check that `main` stays green afterwards.\n\nEvery verdict here comes from `scripts\u002Fharness\u002Ffinalize.py`, which reads git and GitHub; `knowledge\u002Ffinalize.md` explains what each step protects against. A sub-agent's prose is never evidence.\n\n## Input\n\n`$ARGUMENTS`: `\u003Cspec-name> [--alias \u003Cword>] [--release] [--publish]`.\n\n- `--alias`: the short name in the spec's branch names and pull-request titles; reuse the one `\u002Frun-spec` used (default: the spec name).\n- `--release`: also run `\u002Ffinalize-spec-tag` to prepare release notes. `--publish` passes on to it: the maintainer's request to publish the release (`\u002Ffinalize-spec-tag` §Publish).\n\n## Invocation contexts\n\n- **Slash command**: runs Steps 0–8. The merges of the finalize pull request and of any fix pull request are this skill's own, and invoking it is the approval for them.\n- **Model-invoked**: the same.\n- **Non-interactive**: the same, with no questions; every escalation stops the run and returns the stop report. A finalizer that is itself a subagent receives no background notifications: it waits on CI and reviews in the foreground (`finalize.py ci --wait` and `gh pr checks --watch` with a raised Bash timeout), never by ending its turn.\n\n## Sub-skills\n\n| Step | Skill | Writes |\n|---|---|---|\n| 1 | `\u002Ffinalize-spec-verify` | nothing |\n| 2 | `\u002Ffinalize-spec-review` | `## Review Summary` in the spec's `retrospective.md` |\n| 3 | `\u002Ffinalize-spec-retrospective` | the rest of `retrospective.md`; `.claude\u002Fproposals\u002Fpending.md` |\n| 4 | `\u002Ffinalize-spec-publish` (runs `\u002Ffinalize-spec-epic-rollup` and `\u002Fupdate-docs`) | the finalize pull request |\n| 5 | `\u002Ffinalize-spec-verify-ci` | fix pull requests, when main turns red |\n| 6 | `\u002Ffinalize-spec-pm` | approval requests for the backlog |\n| 7 | `\u002Ffinalize-spec-tag` (with `--release`) | nothing public unless `--publish` |\n\n## Step 0 — Worktree\n\nFinalizing never happens in the shared checkout: other sessions use its index and working tree, and a commit there can sweep their work into yours. Every later step reads and writes in the finalize worktree (`\u003Cwt>`).\n\nFirst decide from GitHub, not from memory, whether this is a resumed run: `git fetch origin`, then `gh pr list --state all --head docs\u002F\u003Calias>-finalize --json number,state,mergeCommit`.\n\n- **Merged** finalize pull request (the spec is in `specs\u002Fdone\u002F` on origin\u002Fmain): the record has landed. When the run-events log already holds this spec's `lifecycle` row `unfinalized -> done` with `result: ok` (`grep` it in the main checkout's `.claude\u002Fdata\u002Frun-events.jsonl`), the finalize is complete: report that and stop. Otherwise go straight to Step 5 with its merge commit, then Steps 6–8; `finalize-spec-verify` would rightly refuse a spec already in `done\u002F`. The log is local, so another machine re-runs Steps 5–6, which is safe: a green verdict re-verified is still green, and `pm-sync-core` skips a card already `shipped`.\n- **Open** finalize pull request: use its worktree, or recreate one from the branch (`git worktree add ..\u002F\u003Crepo>-\u003Calias>-finalize docs\u002F\u003Calias>-finalize`), and go straight to `\u002Ffinalize-spec-publish` step 7.\n- **None**, or only closed unmerged ones: a fresh run from Step 1, in a worktree that holds only this run's work:\n  - No branch `docs\u002F\u003Calias>-finalize` and no worktree at the path: `git worktree add -b docs\u002F\u003Calias>-finalize ..\u002F\u003Crepo>-\u003Calias>-finalize origin\u002Fmain`.\n  - A stopped earlier run left them: reuse that worktree. Bring it current with `git -C \u003Cwt> merge origin\u002Fmain`; the steps rewrite everything they own (the Review Summary is replaced, the retrospective's sections rewritten). A branch without a worktree is recreated with `git worktree add ..\u002F\u003Crepo>-\u003Calias>-finalize docs\u002F\u003Calias>-finalize`. Never force-remove either one: a worktree holding changes this skill does not write is an escalation.\n\nRecord the start: `python3 scripts\u002Fharness\u002Frunspec.py event --spec \u003Cspec> --kind lifecycle --detail \"finalize start\"`.\n\n## Steps\n\n1. **Verify** — `\u002Ffinalize-spec-verify \u003Cspec> --alias \u003Calias>`. Continue only on `verdict=ready`.\n2. **Review** — `\u002Ffinalize-spec-review \u003Cspec>`. When it reports open critical findings, stop: each is fixed in its own pull request (below), then `git -C \u003Cwt> merge origin\u002Fmain` and re-run from Step 1, passing the fix pull requests to `\u002Ffinalize-spec-review` as `--extra-pr`.\n3. **Retrospective** — `\u002Ffinalize-spec-retrospective \u003Cspec>`.\n4. **Publish** — `\u002Ffinalize-spec-publish \u003Cspec> --alias \u003Calias>`: move the spec to `done\u002F`, roll up its epic, update the docs and the changelog, open the finalize pull request, answer its review, merge it on `verdict=ready`, confirm it on origin\u002Fmain.\n5. **Verify CI** — `\u002Ffinalize-spec-verify-ci \u003Cspec> --sha \u003Cfinalize merge commit> --alias \u003Calias>`.\n6. **Backlog** — `\u002Ffinalize-spec-pm \u003Cspec>`. It runs after CI is green, because a card is `shipped` only when the code is merged and main is green.\n7. **Release** — with `--release` only: `\u002Ffinalize-spec-tag \u003Cspec> [--publish]`. Without it, report `Release: not requested`.\n8. **Clean up and report.** When the finalize worktree still exists: `git -C \u003Cwt> status --porcelain` prints nothing, then `git worktree remove \u003Cwt>`; when the local branch still exists, `git branch -d docs\u002F\u003Calias>-finalize`. After a squash merge `-d` refuses, because the branch's own commits never reached `main`: leave the branch and name it in the report for the maintainer, never force-delete it. Record `runspec.py event --spec \u003Cspec> --kind lifecycle --detail \"unfinalized -> done\" --result ok`, then print the report.\n\n## Fix pull requests\n\nA confirmed critical review finding (Step 2) or a real CI failure (Step 5) is fixed like a task: one pull request per fix, by the agent that owns the files (`knowledge\u002Fdomains.md`), dispatched with `subagent_type` and `isolation: \"worktree\"`, following `\u002Fimplement` Steps 3–9 but with no task entry. Title it `fix: \u003Cwhat> (\u003Calias> fix)` so `finalize.py verify` sees it while it is open. Merge it on `python3 scripts\u002Fharness\u002Ffinalize.py publish-check --spec \u003Cspec> --pr \u003Cn> --fix` printing `verdict=ready`, then confirm its merge commit on origin\u002Fmain. Print `dispatched=N returned=M failed=K` for every batch of fix dispatches.\n\n## Escalations (the run stops)\n\n1. `finalize-spec-verify` is not ready for a reason no fix pull request can remove: a task incomplete, the spec in the wrong state, the required checks changed, the gate weakened.\n2. A critical finding the fixer cannot resolve, or one that means the spec itself is wrong.\n3. Three review rounds leave the finalize pull request not ready.\n4. `\u002Ffinalize-spec-verify-ci` escalates: an `infra` or `unknown` failure, two fix cycles without green, or a wait budget spent.\n5. A guard blocked this session, or a leak reached a title, body or pushed commit.\n\nThe stop report names the step, the evidence (verbatim, at most ten lines), what is in flight, and the decision needed. The spec stays where it is on origin\u002Fmain; re-running `\u002Ffinalize-spec \u003Cspec>` resumes.\n\n## Output\n\n```text\n## Finalized: \u003Cspec>\n\nVerify:     verdict=ready (\u003Ctasks> tasks, last merge \u003Csha7>, main green)\nReview:     \u003Crange>; findings critical N \u002F important N \u002F suggestion N; open critical 0; vendor \u003Cresult>\nRetro:      specs\u002Fdone\u002F\u003Cspec>\u002Fretrospective.md; proposals \u003Cids or none>\nPublish:    PR #\u003Cn> merged as \u003Csha7>; epic \u003Crolled up | no-op>; docs \u003Cfiles or none>; changelog \u003Centries or none (reason)>\nVerify CI:  \u003Cgreen | green after fix PRs #.. | escalated: reason>\nBacklog:    \u003Cpm-sync lines | PM sync pending (reason)>\nRelease:    \u003Cnot requested | notes prepared at \u003Cpath> | published vX.Y.Z>\ndispatched=\u003CN> returned=\u003CM> failed=\u003CK>\n```\n",{"name":5,"description":7,"argument-hint":24},"\u003Cspec-name> [--alias \u003Cword>] [--release] [--publish]","main","6e250ec86158119da148ddc017b960ed3b2bee2b",".claude\u002Fskills\u002Ffinalize-spec",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 finalize-spec",{"tool":39,"command":40},"bunx","bunx skills add turbokast\u002Fmythhelm --skill finalize-spec",{"tool":42,"command":43},"pnpm","pnpm dlx skills add turbokast\u002Fmythhelm --skill finalize-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fturbokast\u002Fmythhelm\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffinalize-spec\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",[],[]]