[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AH2M97GYFVWPQ365TCWME8":3,"skill-same:01M7AH2M97GYFVWPQ365TCWME8":52},{"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":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7AH2M97GYFVWPQ365TCWME8","sb-release",null,"Close the active milestone — bind the version, run the project's release procedure, judge whether it worked, and finalize the whole milestone once it did.","Huruikagi\u002Fspecbind","Huruikagi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10933612?v=4","01M7AGWP8QKD1EXMV26YA1ESXF","ふるいかぎ","01M7AGWP9WBJ1EEJNQKWB77GN3",2,"MIT","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-release\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sb-release\ndescription: Close the active milestone — bind the version, run the project's release procedure, judge whether it worked, and finalize the whole milestone once it did.\nargument-hint: \"[version]\"\n---\n\n# Release the milestone\n\n## Apply project language style\n\nBefore authoring any artifact or user-facing prose, read:\n\n```sh\nspecbind rule read language-style --for consume\n```\n\nApply returned policy only to natural-language prose. `NO_CHANGE RULE_ABSENT`\nmeans no additional project preference; any `ERROR` line stops the workflow.\n\nThe whole milestone or nothing. There is no partial release and no subset\noption.\n\nYou orchestrate; the CLI owns every mutation of SpecBind state. **SpecBind never\nverifies that a publication happened** — you and the user judge that.\n\n## 1. Read the state and bootstrap release policy once\n\n```sh\nspecbind milestone status\nspecbind adapter read release --for consume\nspecbind adapter read git --for consume\n```\n\nThe Release adapter owns project release work. The Git adapter owns the narrow\nproject checkpoints this run may need; reading it grants no authority beyond\nits current guidance.\n\nClassify the exact Release adapter read result before doing anything else:\n\n1. `NO_CHANGE ADAPTER_ABSENT` or `NO_CHANGE ADAPTER_SCAFFOLD` means the adapter\n   is **unconfigured** and enters the bootstrap flow.\n2. Returned content with the required Front Matter and only whitespace after it\n   is an **explicit empty adapter**. Do not bootstrap it. Continue to core\n   release under the empty-body rule below.\n3. Otherwise the returned active body is project policy.\n\nNever infer that an adapter is unconfigured merely because its returned body\ncontains no instructions. The consumer projection has already distinguished an\ninactive scaffold from the explicit empty state.\n\nFor an unconfigured result, do not bind a version, run release work, or\nfinalize. Read\n[Bootstrap the Release adapter](references\u002Fbootstrap-release-adapter.md)\ncompletely and follow it. Investigate and present the complete replacement\nproposal before stopping for explicit approval; the absence of that approval is\nnot a reason to omit the proposal. After an approved adapter replacement and its\nnarrow checkpoint, stop the invocation. Do not load or continue through the core\nrelease procedure in the same run.\n\nAn adapter whose body is empty after Front Matter and has no scaffold marker is\ndifferent: it explicitly means this project needs no project-specific Prepare,\nPublish, Verify, or After-finalize action. Continue to core release. An active\nbody is project policy; follow it below.\n\n## 2. Bind the version\n\n```sh\nspecbind release preflight\n```\n\n`RELEASE_VERSION_UNBOUND` means no version is bound.\n\n**Ask the user for it. Never invent one.** The label is opaque and\ncase-sensitive — `v1.4.0` and `1.4.0` are *different releases*. Adding or\ndropping a leading `v` to make it look right picks an identity the project did\nnot choose.\n\n```sh\nspecbind milestone bind-release \u003Cversion>\n```\n\nBinding and explicit rebinding are evidence-preserving lifecycle metadata\ntransitions. Rust proves that only the active Roadmap's `target_release`\nchanged, so Specs already at `release_ready` keep their completion freshness and\ntheir original `implementation_revision`. Do not generalize this exception to a\nRoadmap scope or body edit, release-policy change, or project version bump.\n\nA different version already bound needs `--rebind`, which is a deliberate\nreplacement — confirm it explicitly first.\n\nA successful bind or rebind leaves the active Roadmap modified. Before release\npreflight, apply the Git adapter read above to one narrow checkpoint containing\nonly that Roadmap transition. Inspect `git status --short` and the Roadmap diff;\nnever include pre-existing or unrelated paths, never amend, and never push from\nthis checkpoint unless separately authorized.\n\nIf the Git adapter is absent, empty, still carries its scaffold marker, or says\nnot to commit, stop after binding and report that the evidence remains fresh but\nrelease preflight still needs a clean project checkpoint. Do not route around\nthat policy or continue into project release work with a dirty Roadmap.\n\nThen re-run `specbind release preflight` and resolve what it reports. **A\npreflight failure stops the run**; no adapter work happens until it passes.\n\nThis is prose, not a script. You perform what it says; a code block in it is an\nexample to follow, not something that runs on its own.\n\n**An empty adapter means releasing needs no project-specific action.** That is\nan explicit statement, not a gap. Skip sections 3 through 6 and go directly to\nsection 7, core finalization. There is no project publication claim to verify in\nthis branch; the cannot-verify rule applies when active adapter guidance claims\nthat Publish occurred.\n\n(Release keeps this selector-specific empty-body meaning. The installed Git\nadapter is active checkpoint policy; do not transfer either adapter's default\nto the other.)\n\n## 3. Prepare\n\nExecute any applicable Prepare guidance. Repeatable and local — no confirmation\nneeded. If it fails, stop here and report; nothing has left the repository.\n\nPrepare may build ignored packages, but a version bump, generated tracked file,\nor release-specific commit is an ordinary project change after accepted\ncompletion. The Release adapter owns whether such a commit is part of this\nproject's procedure; it cannot keep the old completion evidence fresh. After\nPrepare, rerun:\n\n```sh\nspecbind release preflight\n```\n\nIf the project changed and preflight no longer passes, stop before Publish and\nreport the affected completion handshakes. They must be rerun at the new\nrevision. Never treat a successful Prepare commit as permission to publish stale\ncompletion evidence.\n\n## 4. Publish — confirm with the user first\n\n**This is the release-identity or outward-facing boundary in the workflow.** A\nproject may define Publish as a local annotated tag, or as a deployment, upload,\nsubmission, or remote tag. A local tag has not left the repository, but it\nestablishes the release identity that later work may consume. External actions\nalso become visible to people you cannot reach.\n\nState what the adapter will do, whether it stays local or leaves the repository,\nand to which version, then get confirmation.\n\nDo this **even if the run began with broad instructions.** Authority to prepare a\nrelease is not authority to publish one.\n\n## 5. Verify — it is a completion claim\n\n```sh\nspecbind protocol read completion-verification\n```\n\nThe claim is \"the intended version really was published and is usable\". Hold it\nto the same standard as every other completion claim.\n\n**Re-reading what the publish step reported is not verification.** A publish\ncommand's success output is a claim about itself. Get fresh evidence that the\nthing is actually out there and usable.\n\nIf verification cannot be performed at all — no way to reach the published\nartifact, no credentials — that is *cannot verify*, and it is **not** a pass.\nReport it and do not finalize.\n\n## 6. When publish succeeded but verify did not\n\nThe milestone stays active. Every SpecBind artifact stays as it is. Then:\n\n- **Do not roll back the publication.** SpecBind has no authority over the\n  external system, an unpublish is often impossible or itself destructive, and\n  that decision belongs to the user.\n- **Do not retry blindly.** Read the adapter against *current* external state\n  first. A publish step that partly succeeded may not be idempotent — repeating\n  it can leave a second tag, a duplicate artifact, or a failure that hides the\n  first success.\n\nReport what you observed, say the milestone is still active, and work with the\nuser on reconciling, retrying, or abandoning it.\n\n## 7. Write the summaries and finalize\n\nOne summary per participating Spec — exactly the participating set, no more and\nno fewer.\n\n**The summary says what was delivered, not what was asked for.** The brief is\ndrafting context only: it describes the start of the milestone, and the two\ndiverge routinely — scope gets cut, an approach changes, a requirement appears\nduring design. Check each summary against the final requirements, the active\nrequirement IDs, the design, the completed tasks, and the roadmap scope. This\ntext becomes the Spec's permanent history.\n\nKeep it one line: no carriage return or line feed. Inline Markdown is fine.\n\nImmediately before finalization, record `git status --short`. Finalization\ntargets must be clean, but unrelated dirty paths may exist and must remain\nuntouched.\n\n```sh\nspecbind release finalize --log-entries -\n```\n\n```json\n{\n  \"log_entries\": [\n    { \"spec\": \"cart\", \"summary\": \"Capped held quantities at 99 per SKU.\" }\n  ]\n}\n```\n\nA Direct-only milestone omits the option entirely, or passes an explicit empty\narray.\n\n**Do not pre-edit `log.md`.** The CLI owns the whole structural update — date\nheadings, ordering, the canonical entry wrapper, and idempotent retry matching\nby milestone ID. A failed attempt is retryable and will not duplicate history.\n\n## 8. Checkpoint only the finalized lifecycle metadata\n\nAfter successful finalization, run `git status --short` again and compare it to\nthe snapshot taken immediately before. The newly changed paths are the CLI's\nlog, archive, idle-state, Brief, Research, Tasks, review, and Roadmap lifecycle\ntransaction. They are post-publication metadata; the published tag or package\nmay correctly point to the earlier verified implementation revision.\n\n```sh\nspecbind adapter read git --for consume\n```\n\n`NO_CHANGE ADAPTER_ABSENT`, `NO_CHANGE ADAPTER_SCAFFOLD`, or an empty Git\nadapter means no adapter-directed commit. Leave the finalized metadata\nuncommitted and report it.\n\nWith active guidance, follow it for one local checkpoint containing **only**\nthe paths newly changed by finalization. Never include a path that was already\ndirty, unrelated work, or any After-finalize output. Check the staged diff and\nuse a concise message describing the closed release.\n\nPublication approval does not authorize pushing this commit. Push only when the\nuser explicitly requested it for the current run or an applicable project\ninstruction independently requires it. Never amend, rewrite history, force-push,\nor move the published tag to include this later metadata commit.\n\nIf the paths cannot be separated safely or the commit fails, the release is\nstill finalized. Report the checkpoint failure separately and never rerun\nfinalization merely to obtain a commit.\n\n## 9. After finalize\n\nExecute any applicable After-finalize guidance, and report its result\nseparately. **A failure here is not a failed release** — the milestone is\nalready closed. Never re-run finalization because of it.\n\n### Recommend a post-release configuration review when this milestone earned it\n\nFinalization is the moment a steering edit becomes free again. Before it, a\nsteering change is an ordinary project change that stales every accepted\ncompletion and forces the whole handshake to be re-run. So this belongs here,\nafter finalization succeeded, and nowhere earlier.\n\nSay one sentence recommending a post-release review through `sb-configure` when\nany of these holds. `sb-configure` will determine whether the review should\nupdate Steering, Rules, Templates, Adapters, or another supported surface, and\nwill route the actual change to the owning Skill:\n\n- the milestone's scope included a **new Spec** — the project took on a durable\n  responsibility it did not have before\n- **Contracts changed** during the milestone, so a boundary moved\n- the project has **no steering documents at all** and has now shipped a release\n\nOtherwise say nothing. A release that changed no durable pattern does not need\nthe prompt, and one that appears every time is one nobody reads.\n\nIt is a recommendation. The release is already complete, nothing waits on it,\nand stale steering is never a release failure.\n\n## Boundaries\n\n- Orchestrate only. Author no Spec artifact, edit no `log.md`, approve no gate.\n- **Never claim SpecBind verified an external publication.** It reports only\n  what it can check in the repository.\n- Never invent a release label, and never normalize one the user gave you.\n- Finalize the complete milestone or nothing.\n- Report in the project's language: the version, what the adapter did, what\n  verification showed, what was finalized, and anything left for the user.\n","# Release the milestone\n\n## Apply project language style\n\nBefore authoring any artifact or user-facing prose, read:\n\n```sh\nspecbind rule read language-style --for consume\n```\n\nApply returned policy only to natural-language prose. `NO_CHANGE RULE_ABSENT`\nmeans no additional project preference; any `ERROR` line stops the workflow.\n\nThe whole milestone or nothing. There is no partial release and no subset\noption.\n\nYou orchestrate; the CLI owns every mutation of SpecBind state. **SpecBind never\nverifies that a publication happened** — you and the user judge that.\n\n## 1. Read the state and bootstrap release policy once\n\n```sh\nspecbind milestone status\nspecbind adapter read release --for consume\nspecbind adapter read git --for consume\n```\n\nThe Release adapter owns project release work. The Git adapter owns the narrow\nproject checkpoints this run may need; reading it grants no authority beyond\nits current guidance.\n\nClassify the exact Release adapter read result before doing anything else:\n\n1. `NO_CHANGE ADAPTER_ABSENT` or `NO_CHANGE ADAPTER_SCAFFOLD` means the adapter\n   is **unconfigured** and enters the bootstrap flow.\n2. Returned content with the required Front Matter and only whitespace after it\n   is an **explicit empty adapter**. Do not bootstrap it. Continue to core\n   release under the empty-body rule below.\n3. Otherwise the returned active body is project policy.\n\nNever infer that an adapter is unconfigured merely because its returned body\ncontains no instructions. The consumer projection has already distinguished an\ninactive scaffold from the explicit empty state.\n\nFor an unconfigured result, do not bind a version, run release work, or\nfinalize. Read\n[Bootstrap the Release adapter](references\u002Fbootstrap-release-adapter.md)\ncompletely and follow it. Investigate and present the complete replacement\nproposal before stopping for explicit approval; the absence of that approval is\nnot a reason to omit the proposal. After an approved adapter replacement and its\nnarrow checkpoint, stop the invocation. Do not load or continue through the core\nrelease procedure in the same run.\n\nAn adapter whose body is empty after Front Matter and has no scaffold marker is\ndifferent: it explicitly means this project needs no project-specific Prepare,\nPublish, Verify, or After-finalize action. Continue to core release. An active\nbody is project policy; follow it below.\n\n## 2. Bind the version\n\n```sh\nspecbind release preflight\n```\n\n`RELEASE_VERSION_UNBOUND` means no version is bound.\n\n**Ask the user for it. Never invent one.** The label is opaque and\ncase-sensitive — `v1.4.0` and `1.4.0` are *different releases*. Adding or\ndropping a leading `v` to make it look right picks an identity the project did\nnot choose.\n\n```sh\nspecbind milestone bind-release \u003Cversion>\n```\n\nBinding and explicit rebinding are evidence-preserving lifecycle metadata\ntransitions. Rust proves that only the active Roadmap's `target_release`\nchanged, so Specs already at `release_ready` keep their completion freshness and\ntheir original `implementation_revision`. Do not generalize this exception to a\nRoadmap scope or body edit, release-policy change, or project version bump.\n\nA different version already bound needs `--rebind`, which is a deliberate\nreplacement — confirm it explicitly first.\n\nA successful bind or rebind leaves the active Roadmap modified. Before release\npreflight, apply the Git adapter read above to one narrow checkpoint containing\nonly that Roadmap transition. Inspect `git status --short` and the Roadmap diff;\nnever include pre-existing or unrelated paths, never amend, and never push from\nthis checkpoint unless separately authorized.\n\nIf the Git adapter is absent, empty, still carries its scaffold marker, or says\nnot to commit, stop after binding and report that the evidence remains fresh but\nrelease preflight still needs a clean project checkpoint. Do not route around\nthat policy or continue into project release work with a dirty Roadmap.\n\nThen re-run `specbind release preflight` and resolve what it reports. **A\npreflight failure stops the run**; no adapter work happens until it passes.\n\nThis is prose, not a script. You perform what it says; a code block in it is an\nexample to follow, not something that runs on its own.\n\n**An empty adapter means releasing needs no project-specific action.** That is\nan explicit statement, not a gap. Skip sections 3 through 6 and go directly to\nsection 7, core finalization. There is no project publication claim to verify in\nthis branch; the cannot-verify rule applies when active adapter guidance claims\nthat Publish occurred.\n\n(Release keeps this selector-specific empty-body meaning. The installed Git\nadapter is active checkpoint policy; do not transfer either adapter's default\nto the other.)\n\n## 3. Prepare\n\nExecute any applicable Prepare guidance. Repeatable and local — no confirmation\nneeded. If it fails, stop here and report; nothing has left the repository.\n\nPrepare may build ignored packages, but a version bump, generated tracked file,\nor release-specific commit is an ordinary project change after accepted\ncompletion. The Release adapter owns whether such a commit is part of this\nproject's procedure; it cannot keep the old completion evidence fresh. After\nPrepare, rerun:\n\n```sh\nspecbind release preflight\n```\n\nIf the project changed and preflight no longer passes, stop before Publish and\nreport the affected completion handshakes. They must be rerun at the new\nrevision. Never treat a successful Prepare commit as permission to publish stale\ncompletion evidence.\n\n## 4. Publish — confirm with the user first\n\n**This is the release-identity or outward-facing boundary in the workflow.** A\nproject may define Publish as a local annotated tag, or as a deployment, upload,\nsubmission, or remote tag. A local tag has not left the repository, but it\nestablishes the release identity that later work may consume. External actions\nalso become visible to people you cannot reach.\n\nState what the adapter will do, whether it stays local or leaves the repository,\nand to which version, then get confirmation.\n\nDo this **even if the run began with broad instructions.** Authority to prepare a\nrelease is not authority to publish one.\n\n## 5. Verify — it is a completion claim\n\n```sh\nspecbind protocol read completion-verification\n```\n\nThe claim is \"the intended version really was published and is usable\". Hold it\nto the same standard as every other completion claim.\n\n**Re-reading what the publish step reported is not verification.** A publish\ncommand's success output is a claim about itself. Get fresh evidence that the\nthing is actually out there and usable.\n\nIf verification cannot be performed at all — no way to reach the published\nartifact, no credentials — that is *cannot verify*, and it is **not** a pass.\nReport it and do not finalize.\n\n## 6. When publish succeeded but verify did not\n\nThe milestone stays active. Every SpecBind artifact stays as it is. Then:\n\n- **Do not roll back the publication.** SpecBind has no authority over the\n  external system, an unpublish is often impossible or itself destructive, and\n  that decision belongs to the user.\n- **Do not retry blindly.** Read the adapter against *current* external state\n  first. A publish step that partly succeeded may not be idempotent — repeating\n  it can leave a second tag, a duplicate artifact, or a failure that hides the\n  first success.\n\nReport what you observed, say the milestone is still active, and work with the\nuser on reconciling, retrying, or abandoning it.\n\n## 7. Write the summaries and finalize\n\nOne summary per participating Spec — exactly the participating set, no more and\nno fewer.\n\n**The summary says what was delivered, not what was asked for.** The brief is\ndrafting context only: it describes the start of the milestone, and the two\ndiverge routinely — scope gets cut, an approach changes, a requirement appears\nduring design. Check each summary against the final requirements, the active\nrequirement IDs, the design, the completed tasks, and the roadmap scope. This\ntext becomes the Spec's permanent history.\n\nKeep it one line: no carriage return or line feed. Inline Markdown is fine.\n\nImmediately before finalization, record `git status --short`. Finalization\ntargets must be clean, but unrelated dirty paths may exist and must remain\nuntouched.\n\n```sh\nspecbind release finalize --log-entries -\n```\n\n```json\n{\n  \"log_entries\": [\n    { \"spec\": \"cart\", \"summary\": \"Capped held quantities at 99 per SKU.\" }\n  ]\n}\n```\n\nA Direct-only milestone omits the option entirely, or passes an explicit empty\narray.\n\n**Do not pre-edit `log.md`.** The CLI owns the whole structural update — date\nheadings, ordering, the canonical entry wrapper, and idempotent retry matching\nby milestone ID. A failed attempt is retryable and will not duplicate history.\n\n## 8. Checkpoint only the finalized lifecycle metadata\n\nAfter successful finalization, run `git status --short` again and compare it to\nthe snapshot taken immediately before. The newly changed paths are the CLI's\nlog, archive, idle-state, Brief, Research, Tasks, review, and Roadmap lifecycle\ntransaction. They are post-publication metadata; the published tag or package\nmay correctly point to the earlier verified implementation revision.\n\n```sh\nspecbind adapter read git --for consume\n```\n\n`NO_CHANGE ADAPTER_ABSENT`, `NO_CHANGE ADAPTER_SCAFFOLD`, or an empty Git\nadapter means no adapter-directed commit. Leave the finalized metadata\nuncommitted and report it.\n\nWith active guidance, follow it for one local checkpoint containing **only**\nthe paths newly changed by finalization. Never include a path that was already\ndirty, unrelated work, or any After-finalize output. Check the staged diff and\nuse a concise message describing the closed release.\n\nPublication approval does not authorize pushing this commit. Push only when the\nuser explicitly requested it for the current run or an applicable project\ninstruction independently requires it. Never amend, rewrite history, force-push,\nor move the published tag to include this later metadata commit.\n\nIf the paths cannot be separated safely or the commit fails, the release is\nstill finalized. Report the checkpoint failure separately and never rerun\nfinalization merely to obtain a commit.\n\n## 9. After finalize\n\nExecute any applicable After-finalize guidance, and report its result\nseparately. **A failure here is not a failed release** — the milestone is\nalready closed. Never re-run finalization because of it.\n\n### Recommend a post-release configuration review when this milestone earned it\n\nFinalization is the moment a steering edit becomes free again. Before it, a\nsteering change is an ordinary project change that stales every accepted\ncompletion and forces the whole handshake to be re-run. So this belongs here,\nafter finalization succeeded, and nowhere earlier.\n\nSay one sentence recommending a post-release review through `sb-configure` when\nany of these holds. `sb-configure` will determine whether the review should\nupdate Steering, Rules, Templates, Adapters, or another supported surface, and\nwill route the actual change to the owning Skill:\n\n- the milestone's scope included a **new Spec** — the project took on a durable\n  responsibility it did not have before\n- **Contracts changed** during the milestone, so a boundary moved\n- the project has **no steering documents at all** and has now shipped a release\n\nOtherwise say nothing. A release that changed no durable pattern does not need\nthe prompt, and one that appears every time is one nobody reads.\n\nIt is a recommendation. The release is already complete, nothing waits on it,\nand stale steering is never a release failure.\n\n## Boundaries\n\n- Orchestrate only. Author no Spec artifact, edit no `log.md`, approve no gate.\n- **Never claim SpecBind verified an external publication.** It reports only\n  what it can check in the repository.\n- Never invent a release label, and never normalize one the user gave you.\n- Finalize the complete milestone or nothing.\n- Report in the project's language: the version, what the adapter did, what\n  verification showed, what was finalized, and anything left for the user.\n",{"name":5,"description":7,"argument-hint":24},"[version]","main","2259916910e45633c21f5760d7fe329addc415a7","tools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-release",0,"https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind","https:\u002F\u002Fgithub.com\u002FHuruikagi","2026-11-04 13:59:47",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Huruikagi\u002Fspecbind --skill sb-release",{"tool":38,"command":39},"bunx","bunx skills add Huruikagi\u002Fspecbind --skill sb-release",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Huruikagi\u002Fspecbind --skill sb-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-release\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fbootstrap-release-adapter.md","REFERENCE","参考文档",2567,"https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-release\u002Freferences\u002Fbootstrap-release-adapter.md",[53,59,64,71,78,85],{"skillNo":54,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AH3VQ2VR2X159H99G73TGE","kiro-spec-init","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Ftests\u002Ffixtures\u002Fmigration\u002Fminimal\u002F.agents\u002Fskills\u002Fkiro-spec-init\u002FSKILL.md",[],[],{"skillNo":60,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7AH3RXXAHA50BR132P0M955","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Ftests\u002Ffixtures\u002Fmigration\u002Fguided\u002F.claude\u002Fskills\u002Fkiro-spec-init\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7AH3KZBF4YBG4Q8628WD50S","sb-verify-completion","Consequence-free check of an explicit completion or success claim against fresh evidence. Changes nothing; do not use to advance a named Spec whose implementation may be accepted.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-verify-completion\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7AH3EFD7KC9RGPZFZE0YNA6","sb-validate-implementation","Validate completed Tasks against active Requirement IDs and record completion on GO under an explicit lifecycle-validation request or ordinary Drive authority. Also owns completion withdrawal under an evidenced Drive replan recovery handoff. For a consequence-free claim check, use sb-verify-completion.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-validate-implementation\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7AH38XP0RT7N8G5M74N7FD5","sb-validate-design","Independently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-validate-design\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AH344YTCDM8E8FTSJHC8WF","sb-steering","Maintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-steering\u002FSKILL.md",[],[]]