[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AH344YTCDM8E8FTSJHC8WF":3,"skill-same:01M7AH344YTCDM8E8FTSJHC8WF":46},{"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},"01M7AH344YTCDM8E8FTSJHC8WF","sb-steering",null,"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.","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-steering\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sb-steering\ndescription: 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.\nargument-hint: \"[what changed, or the subject to document]\"\n---\n\n# Maintain durable project guidance\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\nSteering carries what outlives any single change: how this project is built,\nwhat it values, and the constraints every change inherits. You author it. The\nCLI owns discovery and identity.\n\nSteering is not planning-gate evidence, and editing it approves no gate. Like\nany ordinary project-content change, however, a Steering edit stales accepted\ncompletion evidence; follow the authoring protocol's write-safety preflight\nbefore writing. **`sb-discovery` reads the whole collection and\nroutes work on it**, so a document that has quietly gone out of date misroutes\nreal work. Guidance you are not confident is still true is worth removing.\n\n## 1. Confirm what you are doing\n\nThree things can be asked for, and they are not interchangeable:\n\n| Intent | What it means |\n| --- | --- |\n| **Bootstrap** | The project has no steering, and wants a first set |\n| **Synchronize** | Steering exists and the codebase has moved past it |\n| **Add** | One new subject deserves its own document |\n\nAsk when the request does not say. The current inventory is input to that\nconversation, not the answer to it: **an empty `steering\u002F` is a valid steady\nstate**, not a prompt to bootstrap. A project that decided it does not want\nsteering should not get it because a skill assumed.\n\n## 2. Read what exists\n\n```sh\nspecbind steering list\n```\n\nThen read every document it lists:\n\n```sh\nspecbind steering read \u003Cartifact_id> --for maintain\n```\n\nNever read `steering\u002F` directly and never glob it. The selector is the\n`artifact_id`, and the listing is what tells you which ones exist.\n\n**When the listing reports a diagnostic**, `steering read` will refuse every\ndocument, including the healthy ones — a consumer must not act on guidance known\nto be incomplete. You are the exception, and only for repair:\n\n- A malformed-document diagnostic names the faulty path. Read **that file**\n  directly, fix what the diagnostic reports, and re-run\n  `specbind steering list`.\n- A duplicate-identity diagnostic names every colliding path but does not decide\n  which one owns the identity. Read those named files directly and inspect Git\n  history. Remove one only when history proves it is the newly introduced\n  duplicate in the repair scope. Matching content or a copy-like filename is\n  not proof. Without provenance, present every path and the effect of each\n  choice, then stop for the maintainer; do not pick a survivor yourself.\n- Repair first, then continue. Do not work around a broken collection by\n  authoring alongside it.\n- Every other read still goes through the commands above.\n\nRead the project's steering-authoring policy once through its rule surface:\n\n```text\nspecbind rule read steering-principles --for consume\n```\n\nIt covers granularity, examples, and what to leave out. `NO_CHANGE RULE_ABSENT`\nmeans no customization and you proceed on the contract here. Any `ERROR` line\nstops this workflow.\n\n## 3. Understand the codebase before writing about it\n\nDispatch fresh readers rather than reading everything yourself. Each one starts\nwith no context, so give it a brief that stands alone: what to look at, what\nquestion to answer, and that you want the *pattern*, not an inventory.\n\nUse the registered `specbind-researcher` role when available, with ordinary\nfresh readers as the fallback.\nFallback is only for an absent role. A configured role whose model cannot start\nis a configuration or environment failure, not permission to change models.\n\nFor bootstrap, three independent readers cover the ground:\n\n- **Product** — README, package and project metadata, user-facing documentation.\n  What is this for, who uses it, what has it deliberately refused to do?\n- **Technology** — build configuration, dependencies, test setup. What decisions\n  is every change inheriting, and what reasons are recoverable?\n- **Structure** — the tree, naming, import and dependency direction. What rule\n  decides where a new file goes?\n\nFor synchronize, ask each reader to compare the codebase against the steering\ntext you already read, and to report specifics: what steering claims that the\ncode no longer does, and what durable pattern the code has established that\nsteering does not mention.\n\nExtract patterns, not catalogs. **If new code that follows the existing patterns\nwould require a steering update, the document is written at the wrong level.**\n\n## 4. Author\n\nMaterialize from the scaffolds rather than inventing structure:\n\n```sh\nspecbind template list steering\nspecbind template read steering \u003Cselector>\nspecbind protocol read okf-authoring\n```\n\n`product`, `tech`, and `structure` are the bootstrap defaults and carry their own\nidentity. `document` is the scaffold for any other subject and deliberately\ndeclares none.\n\nFollow every scoped instruction the template returns. Follow every\n`create output=\u003Cname>` instruction once to produce its named output. An output\nmay be a short string or a Markdown fragment. Replace every reference to that\nname with the same produced output, and omit `create` comments from the materialized artifact. Treat each\n`maintain` and `consume` comment as one indivisible block: copy its opening\nmarker, complete body, and closing marker byte-for-byte. Never excerpt or\nrewrite it. Existing documents already own their durable comments; preserve\nthem when revising unrelated content.\n\nThe listing reports both a SpecBind-root-relative `output_path` and a\nproject-root-relative `project_path`. Write only to `project_path`. For\n`document`, replace `\u003Cartifact_id>` in that reported project path with the\nidentity you chose; never prepend or remove the configured SpecBind root by\ninference.\n\nAuthor guidance from established project evidence. Do not change source,\nconfiguration, or tests merely to make a statement in the new document true;\nthat would expand a documentation request into implementation work.\n\n### Bootstrap\n\nPropose `product`, `tech`, and `structure`, and say what each would contain\nbefore writing. Nothing privileges these three — the user may rename them, merge\nthem, split them, or decline any of them. Write what the project actually has;\na section you would have to invent content for is a section to delete.\n\n### Synchronize\n\n**Revise in place. Do not accumulate.** A steering document states the project as\nit is now, and guidance that keeps its own history makes readers guess which\nversion is in force. Git holds what it used to say.\n\nThat is not a licence to rewrite:\n\n- Revise what the codebase demonstrably contradicts.\n- Leave alone what is merely not how you would have written it. Restructuring a\n  sound document is churn.\n- When you cannot tell whether something is stale or just unfamiliar, **propose\n  it and let the user decide**. Unclear is not the same as false.\n\nReport drift you are not fixing: patterns the code has established that nobody\nhas decided to make policy are the user's call, not yours.\n\n### Add\n\nFirst establish the subject's current durable convention from project evidence.\nA request to \"write down how we do\" the subject is authority to document an\nexisting practice, not to choose a new policy. If the project has no settled\nconvention, report that absence, ask the maintainer for the actual convention or\nan explicit decision to establish one, and stop before creating a file. Do not\ncombine an accurate statement that tooling is absent with an invented normative\npolicy. After the answer, materialize only the supplied policy and supported\nproject facts.\n\nRead `template read steering document`, choose the identity, and write it only\nto the `project_path` reported by `template list steering` after replacing\n`\u003Cartifact_id>`.\n\nThe identity is yours to choose here — it is the one place SpecBind asks an agent\nto pick an `artifact_id`. Get it right:\n\n- lowercase kebab-case, describing the subject\n- **not** already listed by `specbind steering list`. A duplicate identity is a\n  hard discovery error and drops *both* documents from the collection\n- stable across later renames and moves, because it is the identity, not the file\n  name\n\n## 5. Verify what you wrote\n\n```sh\nspecbind steering list\n```\n\nEvery document you touched must appear, with the selector you intended. **A\ndocument that does not appear was authored wrong** — bad Front Matter, wrong\ntype, or a colliding identity. Fix it and list again. Do not report success on a\ndocument the CLI cannot see.\n\nEvery new Steering document requires a non-empty single-line Front Matter\n`description` naming its lasting project-wide decision boundary. Carry a fixed\ntemplate's literal description into the live document. For the generic `document`\nscaffold or an old template without this field, write the assessed recurring\nresponsibility, checking overlap with existing Steering. Update the description\nwith the body only when that boundary changes. Existing major-one documents\nwithout descriptions remain readable. Descriptions do not narrow Discovery's\nobligation to read all Steering.\n\nFor every newly materialized document, run the mechanical scaffold check with\nthe document identity and the template selector used to create it:\n\n```sh\nspecbind steering check \u003Cartifact_id> --template \u003Cselector>\n```\n\nIt verifies complete durable instruction blocks, leaked `create` guidance,\nunresolved named outputs, and scaffold placeholders. Any `ERROR` stops the\nworkflow; do not recreate this comparison with a project script.\n\n## 6. Checkpoint\n\nThis section is part of completing Steering. A request to stop after Steering or\nafter synchronization still proceeds through this section; it does not mean\nstop with verified files left dirty. Only an explicit instruction that forbids\ncommits skips an otherwise active adapter-directed checkpoint.\n\nAfter every touched Steering document passes the applicable verification above,\nread the active Git adapter:\n\n```sh\nspecbind adapter read git --for consume\n```\n\n`NO_CHANGE ADAPTER_ABSENT` or `NO_CHANGE ADAPTER_SCAFFOLD` means there is no\nadapter-directed checkpoint. Continue to the report with the Steering changes\nleft uncommitted; do not invent a project Git policy.\n\nWhen the adapter has guidance, follow it. The request to perform this mutating\nworkflow authorizes its narrow local checkpoint as the ordinary final step:\n\n- Inspect `git status --short` and the exact diff for every Steering path this\n  run changed.\n- Stage only those verified Steering paths. Never include pre-existing or\n  unrelated changes; if an unrelated change overlaps a touched path, stop\n  before the Git operation and report the conflict.\n- Stay on the current branch. Do not amend, rebase, push, create or switch\n  branches, tag, publish, or rewrite history unless separately authorized.\n- If the checkpoint fails, leave the verified Steering changes in place and\n  report the failed operation. Do not stash, reset, or broaden the commit to\n  manufacture a clean result.\n\n## 7. Report\n\nIn the project's language: what you created or revised, what drift you found and\ndid not act on, anything you deliberately left out, and whether the checkpoint\nwas committed, intentionally absent or scaffolded, or failed. Keep it short —\nthe documents are the deliverable.\n\n## Boundaries\n\n- **Never write secrets.** No credentials, keys, tokens, connection strings, or\n  anything that would be a leak if the repository were public.\n- **Do not document SpecBind's own `settings\u002F` tree or agent directories** such\n  as `.claude\u002F` and `.agents\u002F`. That is project metadata, not project knowledge,\n  and it ages against a tree the project does not maintain.\n- **Do not write transient content.** Current scope, in-flight migrations, and\n  the status of work under way belong to the milestone that owns them. Do not\n  use Spec or milestone state as evidence for Steering content — if you need it\n  to decide what the document says, that content does not belong there. The\n  `specbind milestone status` read required by the authoring protocol is only a\n  write-safety preflight for accepted completion and supplies no document\n  content.\n- Steering is not a gate. This skill approves nothing, records no evidence, and\n  is never required before other work proceeds.\n- Reasoning that changed a routing or scoping decision belongs in that Spec's\n  brief or the Roadmap body, written by the skill that made the decision. Do not\n  relocate it here.\n","# Maintain durable project guidance\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\nSteering carries what outlives any single change: how this project is built,\nwhat it values, and the constraints every change inherits. You author it. The\nCLI owns discovery and identity.\n\nSteering is not planning-gate evidence, and editing it approves no gate. Like\nany ordinary project-content change, however, a Steering edit stales accepted\ncompletion evidence; follow the authoring protocol's write-safety preflight\nbefore writing. **`sb-discovery` reads the whole collection and\nroutes work on it**, so a document that has quietly gone out of date misroutes\nreal work. Guidance you are not confident is still true is worth removing.\n\n## 1. Confirm what you are doing\n\nThree things can be asked for, and they are not interchangeable:\n\n| Intent | What it means |\n| --- | --- |\n| **Bootstrap** | The project has no steering, and wants a first set |\n| **Synchronize** | Steering exists and the codebase has moved past it |\n| **Add** | One new subject deserves its own document |\n\nAsk when the request does not say. The current inventory is input to that\nconversation, not the answer to it: **an empty `steering\u002F` is a valid steady\nstate**, not a prompt to bootstrap. A project that decided it does not want\nsteering should not get it because a skill assumed.\n\n## 2. Read what exists\n\n```sh\nspecbind steering list\n```\n\nThen read every document it lists:\n\n```sh\nspecbind steering read \u003Cartifact_id> --for maintain\n```\n\nNever read `steering\u002F` directly and never glob it. The selector is the\n`artifact_id`, and the listing is what tells you which ones exist.\n\n**When the listing reports a diagnostic**, `steering read` will refuse every\ndocument, including the healthy ones — a consumer must not act on guidance known\nto be incomplete. You are the exception, and only for repair:\n\n- A malformed-document diagnostic names the faulty path. Read **that file**\n  directly, fix what the diagnostic reports, and re-run\n  `specbind steering list`.\n- A duplicate-identity diagnostic names every colliding path but does not decide\n  which one owns the identity. Read those named files directly and inspect Git\n  history. Remove one only when history proves it is the newly introduced\n  duplicate in the repair scope. Matching content or a copy-like filename is\n  not proof. Without provenance, present every path and the effect of each\n  choice, then stop for the maintainer; do not pick a survivor yourself.\n- Repair first, then continue. Do not work around a broken collection by\n  authoring alongside it.\n- Every other read still goes through the commands above.\n\nRead the project's steering-authoring policy once through its rule surface:\n\n```text\nspecbind rule read steering-principles --for consume\n```\n\nIt covers granularity, examples, and what to leave out. `NO_CHANGE RULE_ABSENT`\nmeans no customization and you proceed on the contract here. Any `ERROR` line\nstops this workflow.\n\n## 3. Understand the codebase before writing about it\n\nDispatch fresh readers rather than reading everything yourself. Each one starts\nwith no context, so give it a brief that stands alone: what to look at, what\nquestion to answer, and that you want the *pattern*, not an inventory.\n\nUse the registered `specbind-researcher` role when available, with ordinary\nfresh readers as the fallback.\nFallback is only for an absent role. A configured role whose model cannot start\nis a configuration or environment failure, not permission to change models.\n\nFor bootstrap, three independent readers cover the ground:\n\n- **Product** — README, package and project metadata, user-facing documentation.\n  What is this for, who uses it, what has it deliberately refused to do?\n- **Technology** — build configuration, dependencies, test setup. What decisions\n  is every change inheriting, and what reasons are recoverable?\n- **Structure** — the tree, naming, import and dependency direction. What rule\n  decides where a new file goes?\n\nFor synchronize, ask each reader to compare the codebase against the steering\ntext you already read, and to report specifics: what steering claims that the\ncode no longer does, and what durable pattern the code has established that\nsteering does not mention.\n\nExtract patterns, not catalogs. **If new code that follows the existing patterns\nwould require a steering update, the document is written at the wrong level.**\n\n## 4. Author\n\nMaterialize from the scaffolds rather than inventing structure:\n\n```sh\nspecbind template list steering\nspecbind template read steering \u003Cselector>\nspecbind protocol read okf-authoring\n```\n\n`product`, `tech`, and `structure` are the bootstrap defaults and carry their own\nidentity. `document` is the scaffold for any other subject and deliberately\ndeclares none.\n\nFollow every scoped instruction the template returns. Follow every\n`create output=\u003Cname>` instruction once to produce its named output. An output\nmay be a short string or a Markdown fragment. Replace every reference to that\nname with the same produced output, and omit `create` comments from the materialized artifact. Treat each\n`maintain` and `consume` comment as one indivisible block: copy its opening\nmarker, complete body, and closing marker byte-for-byte. Never excerpt or\nrewrite it. Existing documents already own their durable comments; preserve\nthem when revising unrelated content.\n\nThe listing reports both a SpecBind-root-relative `output_path` and a\nproject-root-relative `project_path`. Write only to `project_path`. For\n`document`, replace `\u003Cartifact_id>` in that reported project path with the\nidentity you chose; never prepend or remove the configured SpecBind root by\ninference.\n\nAuthor guidance from established project evidence. Do not change source,\nconfiguration, or tests merely to make a statement in the new document true;\nthat would expand a documentation request into implementation work.\n\n### Bootstrap\n\nPropose `product`, `tech`, and `structure`, and say what each would contain\nbefore writing. Nothing privileges these three — the user may rename them, merge\nthem, split them, or decline any of them. Write what the project actually has;\na section you would have to invent content for is a section to delete.\n\n### Synchronize\n\n**Revise in place. Do not accumulate.** A steering document states the project as\nit is now, and guidance that keeps its own history makes readers guess which\nversion is in force. Git holds what it used to say.\n\nThat is not a licence to rewrite:\n\n- Revise what the codebase demonstrably contradicts.\n- Leave alone what is merely not how you would have written it. Restructuring a\n  sound document is churn.\n- When you cannot tell whether something is stale or just unfamiliar, **propose\n  it and let the user decide**. Unclear is not the same as false.\n\nReport drift you are not fixing: patterns the code has established that nobody\nhas decided to make policy are the user's call, not yours.\n\n### Add\n\nFirst establish the subject's current durable convention from project evidence.\nA request to \"write down how we do\" the subject is authority to document an\nexisting practice, not to choose a new policy. If the project has no settled\nconvention, report that absence, ask the maintainer for the actual convention or\nan explicit decision to establish one, and stop before creating a file. Do not\ncombine an accurate statement that tooling is absent with an invented normative\npolicy. After the answer, materialize only the supplied policy and supported\nproject facts.\n\nRead `template read steering document`, choose the identity, and write it only\nto the `project_path` reported by `template list steering` after replacing\n`\u003Cartifact_id>`.\n\nThe identity is yours to choose here — it is the one place SpecBind asks an agent\nto pick an `artifact_id`. Get it right:\n\n- lowercase kebab-case, describing the subject\n- **not** already listed by `specbind steering list`. A duplicate identity is a\n  hard discovery error and drops *both* documents from the collection\n- stable across later renames and moves, because it is the identity, not the file\n  name\n\n## 5. Verify what you wrote\n\n```sh\nspecbind steering list\n```\n\nEvery document you touched must appear, with the selector you intended. **A\ndocument that does not appear was authored wrong** — bad Front Matter, wrong\ntype, or a colliding identity. Fix it and list again. Do not report success on a\ndocument the CLI cannot see.\n\nEvery new Steering document requires a non-empty single-line Front Matter\n`description` naming its lasting project-wide decision boundary. Carry a fixed\ntemplate's literal description into the live document. For the generic `document`\nscaffold or an old template without this field, write the assessed recurring\nresponsibility, checking overlap with existing Steering. Update the description\nwith the body only when that boundary changes. Existing major-one documents\nwithout descriptions remain readable. Descriptions do not narrow Discovery's\nobligation to read all Steering.\n\nFor every newly materialized document, run the mechanical scaffold check with\nthe document identity and the template selector used to create it:\n\n```sh\nspecbind steering check \u003Cartifact_id> --template \u003Cselector>\n```\n\nIt verifies complete durable instruction blocks, leaked `create` guidance,\nunresolved named outputs, and scaffold placeholders. Any `ERROR` stops the\nworkflow; do not recreate this comparison with a project script.\n\n## 6. Checkpoint\n\nThis section is part of completing Steering. A request to stop after Steering or\nafter synchronization still proceeds through this section; it does not mean\nstop with verified files left dirty. Only an explicit instruction that forbids\ncommits skips an otherwise active adapter-directed checkpoint.\n\nAfter every touched Steering document passes the applicable verification above,\nread the active Git adapter:\n\n```sh\nspecbind adapter read git --for consume\n```\n\n`NO_CHANGE ADAPTER_ABSENT` or `NO_CHANGE ADAPTER_SCAFFOLD` means there is no\nadapter-directed checkpoint. Continue to the report with the Steering changes\nleft uncommitted; do not invent a project Git policy.\n\nWhen the adapter has guidance, follow it. The request to perform this mutating\nworkflow authorizes its narrow local checkpoint as the ordinary final step:\n\n- Inspect `git status --short` and the exact diff for every Steering path this\n  run changed.\n- Stage only those verified Steering paths. Never include pre-existing or\n  unrelated changes; if an unrelated change overlaps a touched path, stop\n  before the Git operation and report the conflict.\n- Stay on the current branch. Do not amend, rebase, push, create or switch\n  branches, tag, publish, or rewrite history unless separately authorized.\n- If the checkpoint fails, leave the verified Steering changes in place and\n  report the failed operation. Do not stash, reset, or broaden the commit to\n  manufacture a clean result.\n\n## 7. Report\n\nIn the project's language: what you created or revised, what drift you found and\ndid not act on, anything you deliberately left out, and whether the checkpoint\nwas committed, intentionally absent or scaffolded, or failed. Keep it short —\nthe documents are the deliverable.\n\n## Boundaries\n\n- **Never write secrets.** No credentials, keys, tokens, connection strings, or\n  anything that would be a leak if the repository were public.\n- **Do not document SpecBind's own `settings\u002F` tree or agent directories** such\n  as `.claude\u002F` and `.agents\u002F`. That is project metadata, not project knowledge,\n  and it ages against a tree the project does not maintain.\n- **Do not write transient content.** Current scope, in-flight migrations, and\n  the status of work under way belong to the milestone that owns them. Do not\n  use Spec or milestone state as evidence for Steering content — if you need it\n  to decide what the document says, that content does not belong there. The\n  `specbind milestone status` read required by the authoring protocol is only a\n  write-safety preflight for accepted completion and supplies no document\n  content.\n- Steering is not a gate. This skill approves nothing, records no evidence, and\n  is never required before other work proceeds.\n- Reasoning that changed a routing or scoping decision belongs in that Spec's\n  brief or the Roadmap body, written by the skill that made the decision. Do not\n  relocate it here.\n",{"name":5,"description":7,"argument-hint":24},"[what changed, or the subject to document]","main","2259916910e45633c21f5760d7fe329addc415a7","tools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-steering",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-steering",{"tool":38,"command":39},"bunx","bunx skills add Huruikagi\u002Fspecbind --skill sb-steering",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Huruikagi\u002Fspecbind --skill sb-steering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-steering\u002FSKILL.md",true,[],[47,53,58,65,72,79],{"skillNo":48,"name":49,"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":50,"categories":51,"keywords":52,"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":54,"name":49,"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":55,"categories":56,"keywords":57,"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":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AH2YTXST1D1Q1S21V01AVD","sb-status","Report where a Spec or active milestone is in its lifecycle and what can happen next. Read-only; do not use to judge whether completed implementation is actually done.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-status\u002FSKILL.md",[],[]]