[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AH1H6E7HD0MW2PCHRAFPC5":3,"skill-same:01M7AH1H6E7HD0MW2PCHRAFPC5":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AH1H6E7HD0MW2PCHRAFPC5","sb-contract-review",null,"Judge whether the milestone's changes leave every persistent seam in the project coherent, and accept the one contract review that Tasks authoring waits on.","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-contract-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sb-contract-review\ndescription: Judge whether the milestone's changes leave every persistent seam in the project coherent, and accept the one contract review that Tasks authoring waits on.\n---\n\n# Review the contract graph\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\nOne review per milestone, between design approval and any new or revised Tasks\ngate, or between reverse Design approval and adoption finalization. The question is **not** \"do\nthe Specs in this milestone agree with each other.\" It is:\n\n> Does this milestone leave **every** persistent seam in the project coherent —\n> including seams owned by Specs it never touched?\n\nA Spec outside the milestone is the consumer most likely to break, precisely\nbecause nobody is looking at it.\n\nYou accept one artifact. You author no Spec artifact and change no Spec's state.\n\n## 1. Check that the review can run\n\n```sh\nspecbind milestone review status\nspecbind milestone status\nspecbind milestone scope\n```\n\nStop and report, rather than fixing, in these cases:\n\n- **`Status: not_applicable`** — a Direct-only milestone without shared agreement changes has no\n  required review. Say that the review is not required and stop.\n- **A participant is not ready** — use the reported `Milestone kind`. Delivery\n  acceptance needs every Spec-backed item to hold a fresh Design gate and be in\n  `tasks`, `implementation`, or `release_ready`; reverse acceptance needs the same fresh gate and\n  `adoption_ready`, with no Tasks. Route any other state to its phase. Never\n  approve a gate to make this barrier passable.\n\nA delivery participant may retain `tasks.yaml`, including execution progress,\nfrom work approved against the previous review. That file is not a review input:\ndo not read, validate, edit, move, or delete it. Its presence does not weaken or\nblock this judgment. Affected Tasks are reviewed and repaired by their owner\nonly after this Contract Review is accepted. Unaffected later-state participants\nkeep their current Tasks gate and progress.\n\n`milestone scope` gives you the complete current scope. For every Spec-backed\nparticipant it names, also run:\n\n```sh\nspecbind spec status \u003Cspec>\n```\n\n`milestone status` gives you the two revisions you need:\n\n```text\n  Revision: \u003Ccurrent HEAD>\n  Baseline: \u003Cwhat this milestone is measured against>\n```\n\n## 2. Establish what changed\n\n```sh\nspecbind schema read contract\u002Fv1\nspecbind protocol read contract-review\nspecbind contract diff --baseline \u003Cbaseline> --json\n```\n\nAlso read `specbind contract shared read` and\n`specbind contract shared consumers`; use `specbind schema read contract\u002Fv2`\nand `specbind schema read shared-contract\u002Fv1` for their structures. Compare the\nshared manifest at the baseline, including its creation\u002Fdeletion, with scoped\n`sharedContractChanges` and the complete Roadmap body. A planned shared change\nrequires review even with no Spec-backed participant. Shared resource use is\nnot co-ownership; normal catalog values are implementation, not agreement edits.\nShared rules are reviewed here, never executed as shell instructions. Route\ndelivery shared agreement findings to `sb-plan --shared`, and affected Spec work\nto its Design owner. In reverse establishment, read the confirmed proposal in\n`\u003CspecDir>\u002Fadoption\u002Freverse-discovery.yaml` for shared scope instead of delivery\nDirect fields; return findings to the owning `sb-adopt` continuation within\nthat confirmed scope. Do not invent a shared Spec or accept unscoped changes.\n\nRead **every** current Contract in the project, not only the participants':\n\n```sh\nspecbind spec list\nspecbind artifact read \u003Cspec> contract --for consume\n```\n\nUse the diff's `documents` (complete normalized before\u002Fafter manifests and exact\npaths), changed `entries`, `baselineConsumers`, and `currentConsumers` as the\ncomparison input. The CLI compares the complete persistent Spec set and optional\nshared Contract, including baseline-only Specs and empty-manifest creation or\nremoval. It distinguishes a genuinely new Spec from a missing required Contract.\nDo not reconstruct this comparison with `git show` or infer artifact identity.\n\nThe baseline must be the Milestone's reported baseline, not a convenient newer\ncommit. `currentRevision` identifies HEAD; `currentSource: worktree` includes\nuncommitted proposals, and `currentFingerprint` identifies the compared inputs.\nAn input error stops the review without a fallback comparison. Rerun and reassess\nif HEAD or Contract inputs change during review.\n\nThe diff reports reference errors as `diagnostics` so removed targets still name\ntheir consumers. Those errors are findings, not permission to accept. Also run:\n\n```sh\nspecbind check contracts\n```\n\nUse its complete current-graph diagnostics with the diff to route findings below.\nAn exit-zero diff is evidence that comparison succeeded, never a review verdict.\nConsumer lists contain declared direct managed references on each side only;\nexternal consumers and semantic impact still require your judgment.\n\n**The difference is the entry point.** A run that never established what changed\nhas not performed the review, however carefully it read the current graph.\n\nThe Roadmap scope is the second half of that comparison. Match each participant's\nscoped behavior to the current Contract even when its Contract diff is empty. A\nnew owned boundary, exported behavior, consumed seam, invariant, or file-ownership\nclaim that appears in scope but nowhere in the Contract is a finding, not proof\nthat the seam stayed unchanged.\n\nRead the project's seam policy through its project-owned rule surface:\n\n```text\nspecbind rule read contract-principles --for consume\n```\n\nIt covers shared ownership, compatibility posture, generated boundaries, and\ndependency direction. `NO_CHANGE RULE_ABSENT` means no customization; the\nprotocol still applies. Any `ERROR` line stops the review.\n\nDo not read steering here. Whether a design followed project guidance belongs to\nthe design phase and to `sb-validate-design`. Your question is whether the\ngraph is coherent against itself and its consumers.\n\n## 3. Judge\n\nThe protocol owns the judgment. For each changed, added, or removed entry,\nestablish who depends on it and what the change does to them.\n\nFor an unchanged Contract, establish that the scoped behavior introduces no\nmissing persistent seam or guarantee. If scope suggests one, go deeper into the\nrelevant Requirements or Design and declare that artifact in `deepInputs`. Do\nnot accept merely because there is no Contract diff; leave the omission for the\nowning Design phase to resolve.\n\nTwo things the CLI cannot do for you:\n\n**Ownership overlaps and dependency cycles are warnings**, because they are\nsometimes deliberate. Say why the overlap is acceptable, or treat it as a\nfinding. Reporting the warning back is not a judgment.\n\n**External consumers.** A published interface, another repository, a stored data\nshape, an operational contract — none of these are Specs, and nothing will\ndetect the impact. Name the affected consumer, state the impact, and bring it to\nthe user when the change requires a decision they own.\n\nDo not ask the user to repeat a decision already explicit in the delivery\nrequest. If the requested behavior itself changes an exported seam, repository\nevidence finds no managed consumer, and no external consumer is identified by\nthe project, record the possible unmanaged impact and the user's requested\ndisposition in the assessment. Likewise, a request that directly uses or changes\nan existing unconsumed export is evidence to keep that seam for this milestone.\nAsk only when the impact introduces a choice the request did not settle.\n\nSilence here is the one finding with no downstream check that might catch it.\n\n### Go deeper only when the conclusion depends on it\n\nWhen the Contract difference and the current graph settle the question, that is\nthe complete review. Reading Requirements or Design is for when they do not.\n\nDiscover the Spec's artifact selectors before a deep read; never shorten\n`design\u002F\u003Cartifact-id>` to a guessed `design` selector:\n\n```sh\nspecbind artifact list \u003Cspec>\nspecbind artifact read \u003Cspec> requirements --for consume\nspecbind artifact read \u003Cspec> design\u002F\u003Cartifact-id> --for consume\n```\n\nRun the listing before constructing any Design selector and use only the exact\nselectors it reports. Lifecycle states and action labels such as `tasks` and\n`implementation` are not artifact IDs; never turn them into `design\u002Ftasks` or\n`design\u002Fimplementation`.\n\nRead only the Requirements or listed Designs the conclusion needs.\n\nFor `deepInputs`, prefix the exact logical selector reported by `artifact list`\nwith `specs\u002F\u003Ccanonical-spec>#`. Thus `requirements` becomes\n`specs\u002F\u003Cspec>#requirements`, and `design\u002Fmain` becomes\n`specs\u002F\u003Cspec>#design\u002Fmain`. Do not use the reported filesystem `path`, shorten a\nDesign selector, or derive a selector from lifecycle state.\n\nDeclare in `deepInputs` only what the judgment actually relied on. Every declared\ninput is fingerprinted into the accepted artifact, so it becomes a freshness\ninput: editing it later makes the review stale and blocks tasks approval,\nimplementation validation, and release preflight. A file declared because you\nopened it buys recurring invalidation for nothing.\n\nTask plans are never inputs, and the CLI rejects them.\n\n## 4. Remediate, at most twice\n\nWhen dispatched with explicit Drive replan authority, report in-scope\nDesign\u002FContract findings to the `sb-plan` recovery owner with the affected\nSpecs and exact rewind cost. That owner handles retained Tasks after this barrier,\nDesign validation, and return to this review without another user confirmation.\nDo not delete plans or invalidate gates in the review dispatch. Carry the\nfinding history and remaining two-round budget back; recovery never resets it.\nRequirements or Milestone scope changes and unsettled external consequences\nremain user decisions. The explicit-confirmation instructions below apply\noutside that delegated recovery.\n\nIf the review does not pass, you may remediate and rerun **at most two rounds**.\nAfter that, the affected Specs stay in design, no artifact is written, and you\nreport what is unresolved.\n\n**You do not author another phase's artifacts or mutate its state, except for\nthe proven Design-rewind handoff below.** Where a Spec needs owned work:\n\n- present the affected Spec and what is wrong with the seam;\n- before every gate invalidation, present the exact Requirements, Design,\n  Tasks, completion, and accepted Contract Review state that the rewind removes,\n  then obtain explicit user confirmation even when milestone scope is unchanged;\n- name the owning phase and transfer the complete finding and authority described\n  below rather than editing an artifact or lifecycle file.\n\nA Spec added to scope must be brought through design **before** acceptance. It\ncannot be left as follow-up behind a passing review: the accepted artifact has no\nfield a caveat could live in.\n\nNever edit another Spec's contract to make the graph resolve.\n\nThe Design phase owns both the Design set and `contract.yaml`; status has no\nseparate Contract gate. If Requirements remain valid and the finding requires a\nDesign or Contract change, present the complete rewind cost, obtain explicit\nconfirmation, run `specbind spec design invalidate \u003Cspec>`, and hand the work to\n`sb-plan` in explicit Design-phase mode. Never leave the maintainer to infer the\nowning phase from the gate list.\n\nFor that Design invalidation handoff, record `git status --short` before the\ncommand and require the target `spec.yaml` and accepted-review path to be\nunchanged. Immediately after success, capture `specbind spec status \u003Cspec>`, the\nexact lifecycle changed-path set, and its Git diff. Pass those paths and diff to `sb-plan`\nas the Design-rewind delta. Do not edit, discard, stash, or commit it separately;\nthe Design approval checkpoint closes it after independent validation. Any\npre-existing or later-mismatched lifecycle delta is not phase-owned.\n\nA response that stops on this finding is incomplete unless it names the Design\nphase as owner, enumerates the current state that invalidation removes, and gives\nthe exact `specbind spec design invalidate \u003Cspec>` operation before asking for\nconfirmation. Include those facts in the reported outcome even when no file or\nstate changed during the review.\n\nIf Requirements must change, present the complete Requirements rewind cost and\nobtain explicit confirmation, but **do not invoke**\n`specbind spec requirements invalidate \u003Cspec>`. Dispatch `sb-plan` in explicit\nRequirements-phase mode with the exact finding, target Spec, exact command, and\nthe user's operation-specific confirmation. That relayed confirmation authorizes\nthe Requirements receiver to invoke that one command in the current state; it is\nnot general delegation and expires if the finding, state, or rewind cost changes.\nThe Requirements phase owns the invalidation, repair, approval, and one coherent\ncheckpoint containing every path it produced. Carry this review's finding ledger\nand remaining remediation budget through the handoff, then resume review only\nafter the normal Plan route returns all participants to current Design approval.\n\nIf the finding changes milestone scope, produce a complete scope-remediation\nproposal and route it to `sb-discovery`. **Do not invoke**\n`specbind milestone update-scope` from Contract Review. Discovery owns its normal\nscope confirmation, the complete replacement, any lifecycle invalidations, every\nnew or changed Brief, and its checkpoint. Plan is a later, separately authorized\nroute for affected Specs. Resume Contract Review only after the updated complete\nparticipant set reaches current Design approval. Never remove completed Direct\nitems, retained Tasks, or another Spec's progress to make the proposal fit.\n\n## 5. Write the assessment and accept\n\nThe assessment is the durable explanation. Write it so a reader who did not\nparticipate can tell what was examined and why the conclusion holds: what changed\nin the graph relative to the baseline, who depends on each change, and why the\nseams are coherent.\n\n**A short assessment is often the correct one.** One participating Spec whose\nContract is unchanged is a complete review only after the scoped behavior has\nbeen checked for a missing persistent seam or guarantee. When none is missing,\nthe review answered the same question and the answer was brief. Padding it\nproduces a record whose length implies scrutiny that did not happen.\n\nPresent the assessment and any findings before you accept.\n\n```sh\nspecbind milestone review accept --candidate -\n```\n\nThe candidate is strict JSON on stdin:\n\n```json\n{\n  \"schemaVersion\": 1,\n  \"assessment\": \"...Markdown...\",\n  \"deepInputs\": [\"specs\u002Fcheckout#design\u002Fmain\"]\n}\n```\n\n`deepInputs` may be empty. Selectors are canonical requirements or design\nartifacts only. The CLI resolves every path, computes every fingerprint, and\nowns the timestamp — never supply your own.\n\n### On authority\n\nAcceptance takes no approval mode, and that is deliberate rather than an\noversight. The accepted artifact records `type`, `milestone_id`, `passed_at`, and\n`input_revisions` — there is no field for a user's approval, so this is your\njudgment being recorded, not their authorization.\n\nThat is not licence to accept quietly. Present your reasoning first, and stop for\nthe user whenever a finding needs a decision they own — external consumer impact,\nor a scope change.\n\n**There is no partial, conditional, or provisional acceptance.** An unresolved\nfinding means the review has not passed. Accepting anyway records a judgment that\nwas not made, and every later boundary will trust it.\n\n## 6. Checkpoint\n\nOnly after acceptance succeeds is this work eligible to commit.\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 commit. Stop there — that is an answer, not a missing file to\nwork around.\n\nWhen the adapter has guidance, follow it. The request to perform this mutating\nphase authorizes the adapter's narrow local checkpoint as its ordinary final\nstep. It does not authorize anything broader:\n\n- An explicit user or root instruction that forbids commits wins, and tool\n  permissions still apply.\n- Commit guidance is not push guidance. Push only where the adapter says to, and\n  never force-push, rewrite history, or bypass a protected branch.\n- Stage only the paths this run produced. Unrelated work already in the worktree\n  is left exactly as it is.\n- Stop before the Git operation if the guidance is ambiguous, unsafe, or\n  conflicts with something else you were told.\n\nA failed checkpoint does not undo the acceptance. Report the work as uncommitted\nand continue.\n\n## Boundaries\n\n- Author no Spec artifact. Requirements, design, and contracts belong to their\n  phases; `tasks.yaml` belongs to the phase after this one.\n- Write no machine state. Never edit `spec.yaml` or the roadmap directly.\n- Never read, delete, or repair a delivery task plan, and never approve or\n  invalidate a gate to make this barrier passable. Invalidation happens only as the explicitly user-confirmed\n  outcome of a finding after its complete rewind cost was presented.\n- Report in the project's language: what changed in the graph, who is affected,\n  what you concluded, anything you brought to the user, whether the review was\n  accepted, and what runs next.\n","# Review the contract graph\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\nOne review per milestone, between design approval and any new or revised Tasks\ngate, or between reverse Design approval and adoption finalization. The question is **not** \"do\nthe Specs in this milestone agree with each other.\" It is:\n\n> Does this milestone leave **every** persistent seam in the project coherent —\n> including seams owned by Specs it never touched?\n\nA Spec outside the milestone is the consumer most likely to break, precisely\nbecause nobody is looking at it.\n\nYou accept one artifact. You author no Spec artifact and change no Spec's state.\n\n## 1. Check that the review can run\n\n```sh\nspecbind milestone review status\nspecbind milestone status\nspecbind milestone scope\n```\n\nStop and report, rather than fixing, in these cases:\n\n- **`Status: not_applicable`** — a Direct-only milestone without shared agreement changes has no\n  required review. Say that the review is not required and stop.\n- **A participant is not ready** — use the reported `Milestone kind`. Delivery\n  acceptance needs every Spec-backed item to hold a fresh Design gate and be in\n  `tasks`, `implementation`, or `release_ready`; reverse acceptance needs the same fresh gate and\n  `adoption_ready`, with no Tasks. Route any other state to its phase. Never\n  approve a gate to make this barrier passable.\n\nA delivery participant may retain `tasks.yaml`, including execution progress,\nfrom work approved against the previous review. That file is not a review input:\ndo not read, validate, edit, move, or delete it. Its presence does not weaken or\nblock this judgment. Affected Tasks are reviewed and repaired by their owner\nonly after this Contract Review is accepted. Unaffected later-state participants\nkeep their current Tasks gate and progress.\n\n`milestone scope` gives you the complete current scope. For every Spec-backed\nparticipant it names, also run:\n\n```sh\nspecbind spec status \u003Cspec>\n```\n\n`milestone status` gives you the two revisions you need:\n\n```text\n  Revision: \u003Ccurrent HEAD>\n  Baseline: \u003Cwhat this milestone is measured against>\n```\n\n## 2. Establish what changed\n\n```sh\nspecbind schema read contract\u002Fv1\nspecbind protocol read contract-review\nspecbind contract diff --baseline \u003Cbaseline> --json\n```\n\nAlso read `specbind contract shared read` and\n`specbind contract shared consumers`; use `specbind schema read contract\u002Fv2`\nand `specbind schema read shared-contract\u002Fv1` for their structures. Compare the\nshared manifest at the baseline, including its creation\u002Fdeletion, with scoped\n`sharedContractChanges` and the complete Roadmap body. A planned shared change\nrequires review even with no Spec-backed participant. Shared resource use is\nnot co-ownership; normal catalog values are implementation, not agreement edits.\nShared rules are reviewed here, never executed as shell instructions. Route\ndelivery shared agreement findings to `sb-plan --shared`, and affected Spec work\nto its Design owner. In reverse establishment, read the confirmed proposal in\n`\u003CspecDir>\u002Fadoption\u002Freverse-discovery.yaml` for shared scope instead of delivery\nDirect fields; return findings to the owning `sb-adopt` continuation within\nthat confirmed scope. Do not invent a shared Spec or accept unscoped changes.\n\nRead **every** current Contract in the project, not only the participants':\n\n```sh\nspecbind spec list\nspecbind artifact read \u003Cspec> contract --for consume\n```\n\nUse the diff's `documents` (complete normalized before\u002Fafter manifests and exact\npaths), changed `entries`, `baselineConsumers`, and `currentConsumers` as the\ncomparison input. The CLI compares the complete persistent Spec set and optional\nshared Contract, including baseline-only Specs and empty-manifest creation or\nremoval. It distinguishes a genuinely new Spec from a missing required Contract.\nDo not reconstruct this comparison with `git show` or infer artifact identity.\n\nThe baseline must be the Milestone's reported baseline, not a convenient newer\ncommit. `currentRevision` identifies HEAD; `currentSource: worktree` includes\nuncommitted proposals, and `currentFingerprint` identifies the compared inputs.\nAn input error stops the review without a fallback comparison. Rerun and reassess\nif HEAD or Contract inputs change during review.\n\nThe diff reports reference errors as `diagnostics` so removed targets still name\ntheir consumers. Those errors are findings, not permission to accept. Also run:\n\n```sh\nspecbind check contracts\n```\n\nUse its complete current-graph diagnostics with the diff to route findings below.\nAn exit-zero diff is evidence that comparison succeeded, never a review verdict.\nConsumer lists contain declared direct managed references on each side only;\nexternal consumers and semantic impact still require your judgment.\n\n**The difference is the entry point.** A run that never established what changed\nhas not performed the review, however carefully it read the current graph.\n\nThe Roadmap scope is the second half of that comparison. Match each participant's\nscoped behavior to the current Contract even when its Contract diff is empty. A\nnew owned boundary, exported behavior, consumed seam, invariant, or file-ownership\nclaim that appears in scope but nowhere in the Contract is a finding, not proof\nthat the seam stayed unchanged.\n\nRead the project's seam policy through its project-owned rule surface:\n\n```text\nspecbind rule read contract-principles --for consume\n```\n\nIt covers shared ownership, compatibility posture, generated boundaries, and\ndependency direction. `NO_CHANGE RULE_ABSENT` means no customization; the\nprotocol still applies. Any `ERROR` line stops the review.\n\nDo not read steering here. Whether a design followed project guidance belongs to\nthe design phase and to `sb-validate-design`. Your question is whether the\ngraph is coherent against itself and its consumers.\n\n## 3. Judge\n\nThe protocol owns the judgment. For each changed, added, or removed entry,\nestablish who depends on it and what the change does to them.\n\nFor an unchanged Contract, establish that the scoped behavior introduces no\nmissing persistent seam or guarantee. If scope suggests one, go deeper into the\nrelevant Requirements or Design and declare that artifact in `deepInputs`. Do\nnot accept merely because there is no Contract diff; leave the omission for the\nowning Design phase to resolve.\n\nTwo things the CLI cannot do for you:\n\n**Ownership overlaps and dependency cycles are warnings**, because they are\nsometimes deliberate. Say why the overlap is acceptable, or treat it as a\nfinding. Reporting the warning back is not a judgment.\n\n**External consumers.** A published interface, another repository, a stored data\nshape, an operational contract — none of these are Specs, and nothing will\ndetect the impact. Name the affected consumer, state the impact, and bring it to\nthe user when the change requires a decision they own.\n\nDo not ask the user to repeat a decision already explicit in the delivery\nrequest. If the requested behavior itself changes an exported seam, repository\nevidence finds no managed consumer, and no external consumer is identified by\nthe project, record the possible unmanaged impact and the user's requested\ndisposition in the assessment. Likewise, a request that directly uses or changes\nan existing unconsumed export is evidence to keep that seam for this milestone.\nAsk only when the impact introduces a choice the request did not settle.\n\nSilence here is the one finding with no downstream check that might catch it.\n\n### Go deeper only when the conclusion depends on it\n\nWhen the Contract difference and the current graph settle the question, that is\nthe complete review. Reading Requirements or Design is for when they do not.\n\nDiscover the Spec's artifact selectors before a deep read; never shorten\n`design\u002F\u003Cartifact-id>` to a guessed `design` selector:\n\n```sh\nspecbind artifact list \u003Cspec>\nspecbind artifact read \u003Cspec> requirements --for consume\nspecbind artifact read \u003Cspec> design\u002F\u003Cartifact-id> --for consume\n```\n\nRun the listing before constructing any Design selector and use only the exact\nselectors it reports. Lifecycle states and action labels such as `tasks` and\n`implementation` are not artifact IDs; never turn them into `design\u002Ftasks` or\n`design\u002Fimplementation`.\n\nRead only the Requirements or listed Designs the conclusion needs.\n\nFor `deepInputs`, prefix the exact logical selector reported by `artifact list`\nwith `specs\u002F\u003Ccanonical-spec>#`. Thus `requirements` becomes\n`specs\u002F\u003Cspec>#requirements`, and `design\u002Fmain` becomes\n`specs\u002F\u003Cspec>#design\u002Fmain`. Do not use the reported filesystem `path`, shorten a\nDesign selector, or derive a selector from lifecycle state.\n\nDeclare in `deepInputs` only what the judgment actually relied on. Every declared\ninput is fingerprinted into the accepted artifact, so it becomes a freshness\ninput: editing it later makes the review stale and blocks tasks approval,\nimplementation validation, and release preflight. A file declared because you\nopened it buys recurring invalidation for nothing.\n\nTask plans are never inputs, and the CLI rejects them.\n\n## 4. Remediate, at most twice\n\nWhen dispatched with explicit Drive replan authority, report in-scope\nDesign\u002FContract findings to the `sb-plan` recovery owner with the affected\nSpecs and exact rewind cost. That owner handles retained Tasks after this barrier,\nDesign validation, and return to this review without another user confirmation.\nDo not delete plans or invalidate gates in the review dispatch. Carry the\nfinding history and remaining two-round budget back; recovery never resets it.\nRequirements or Milestone scope changes and unsettled external consequences\nremain user decisions. The explicit-confirmation instructions below apply\noutside that delegated recovery.\n\nIf the review does not pass, you may remediate and rerun **at most two rounds**.\nAfter that, the affected Specs stay in design, no artifact is written, and you\nreport what is unresolved.\n\n**You do not author another phase's artifacts or mutate its state, except for\nthe proven Design-rewind handoff below.** Where a Spec needs owned work:\n\n- present the affected Spec and what is wrong with the seam;\n- before every gate invalidation, present the exact Requirements, Design,\n  Tasks, completion, and accepted Contract Review state that the rewind removes,\n  then obtain explicit user confirmation even when milestone scope is unchanged;\n- name the owning phase and transfer the complete finding and authority described\n  below rather than editing an artifact or lifecycle file.\n\nA Spec added to scope must be brought through design **before** acceptance. It\ncannot be left as follow-up behind a passing review: the accepted artifact has no\nfield a caveat could live in.\n\nNever edit another Spec's contract to make the graph resolve.\n\nThe Design phase owns both the Design set and `contract.yaml`; status has no\nseparate Contract gate. If Requirements remain valid and the finding requires a\nDesign or Contract change, present the complete rewind cost, obtain explicit\nconfirmation, run `specbind spec design invalidate \u003Cspec>`, and hand the work to\n`sb-plan` in explicit Design-phase mode. Never leave the maintainer to infer the\nowning phase from the gate list.\n\nFor that Design invalidation handoff, record `git status --short` before the\ncommand and require the target `spec.yaml` and accepted-review path to be\nunchanged. Immediately after success, capture `specbind spec status \u003Cspec>`, the\nexact lifecycle changed-path set, and its Git diff. Pass those paths and diff to `sb-plan`\nas the Design-rewind delta. Do not edit, discard, stash, or commit it separately;\nthe Design approval checkpoint closes it after independent validation. Any\npre-existing or later-mismatched lifecycle delta is not phase-owned.\n\nA response that stops on this finding is incomplete unless it names the Design\nphase as owner, enumerates the current state that invalidation removes, and gives\nthe exact `specbind spec design invalidate \u003Cspec>` operation before asking for\nconfirmation. Include those facts in the reported outcome even when no file or\nstate changed during the review.\n\nIf Requirements must change, present the complete Requirements rewind cost and\nobtain explicit confirmation, but **do not invoke**\n`specbind spec requirements invalidate \u003Cspec>`. Dispatch `sb-plan` in explicit\nRequirements-phase mode with the exact finding, target Spec, exact command, and\nthe user's operation-specific confirmation. That relayed confirmation authorizes\nthe Requirements receiver to invoke that one command in the current state; it is\nnot general delegation and expires if the finding, state, or rewind cost changes.\nThe Requirements phase owns the invalidation, repair, approval, and one coherent\ncheckpoint containing every path it produced. Carry this review's finding ledger\nand remaining remediation budget through the handoff, then resume review only\nafter the normal Plan route returns all participants to current Design approval.\n\nIf the finding changes milestone scope, produce a complete scope-remediation\nproposal and route it to `sb-discovery`. **Do not invoke**\n`specbind milestone update-scope` from Contract Review. Discovery owns its normal\nscope confirmation, the complete replacement, any lifecycle invalidations, every\nnew or changed Brief, and its checkpoint. Plan is a later, separately authorized\nroute for affected Specs. Resume Contract Review only after the updated complete\nparticipant set reaches current Design approval. Never remove completed Direct\nitems, retained Tasks, or another Spec's progress to make the proposal fit.\n\n## 5. Write the assessment and accept\n\nThe assessment is the durable explanation. Write it so a reader who did not\nparticipate can tell what was examined and why the conclusion holds: what changed\nin the graph relative to the baseline, who depends on each change, and why the\nseams are coherent.\n\n**A short assessment is often the correct one.** One participating Spec whose\nContract is unchanged is a complete review only after the scoped behavior has\nbeen checked for a missing persistent seam or guarantee. When none is missing,\nthe review answered the same question and the answer was brief. Padding it\nproduces a record whose length implies scrutiny that did not happen.\n\nPresent the assessment and any findings before you accept.\n\n```sh\nspecbind milestone review accept --candidate -\n```\n\nThe candidate is strict JSON on stdin:\n\n```json\n{\n  \"schemaVersion\": 1,\n  \"assessment\": \"...Markdown...\",\n  \"deepInputs\": [\"specs\u002Fcheckout#design\u002Fmain\"]\n}\n```\n\n`deepInputs` may be empty. Selectors are canonical requirements or design\nartifacts only. The CLI resolves every path, computes every fingerprint, and\nowns the timestamp — never supply your own.\n\n### On authority\n\nAcceptance takes no approval mode, and that is deliberate rather than an\noversight. The accepted artifact records `type`, `milestone_id`, `passed_at`, and\n`input_revisions` — there is no field for a user's approval, so this is your\njudgment being recorded, not their authorization.\n\nThat is not licence to accept quietly. Present your reasoning first, and stop for\nthe user whenever a finding needs a decision they own — external consumer impact,\nor a scope change.\n\n**There is no partial, conditional, or provisional acceptance.** An unresolved\nfinding means the review has not passed. Accepting anyway records a judgment that\nwas not made, and every later boundary will trust it.\n\n## 6. Checkpoint\n\nOnly after acceptance succeeds is this work eligible to commit.\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 commit. Stop there — that is an answer, not a missing file to\nwork around.\n\nWhen the adapter has guidance, follow it. The request to perform this mutating\nphase authorizes the adapter's narrow local checkpoint as its ordinary final\nstep. It does not authorize anything broader:\n\n- An explicit user or root instruction that forbids commits wins, and tool\n  permissions still apply.\n- Commit guidance is not push guidance. Push only where the adapter says to, and\n  never force-push, rewrite history, or bypass a protected branch.\n- Stage only the paths this run produced. Unrelated work already in the worktree\n  is left exactly as it is.\n- Stop before the Git operation if the guidance is ambiguous, unsafe, or\n  conflicts with something else you were told.\n\nA failed checkpoint does not undo the acceptance. Report the work as uncommitted\nand continue.\n\n## Boundaries\n\n- Author no Spec artifact. Requirements, design, and contracts belong to their\n  phases; `tasks.yaml` belongs to the phase after this one.\n- Write no machine state. Never edit `spec.yaml` or the roadmap directly.\n- Never read, delete, or repair a delivery task plan, and never approve or\n  invalidate a gate to make this barrier passable. Invalidation happens only as the explicitly user-confirmed\n  outcome of a finding after its complete rewind cost was presented.\n- Report in the project's language: what changed in the graph, who is affected,\n  what you concluded, anything you brought to the user, whether the review was\n  accepted, and what runs next.\n",{"name":5,"description":7},"main","2259916910e45633c21f5760d7fe329addc415a7","tools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-contract-review",0,"https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind","https:\u002F\u002Fgithub.com\u002FHuruikagi","2026-11-04 13:59:47",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Huruikagi\u002Fspecbind --skill sb-contract-review",{"tool":37,"command":38},"bunx","bunx skills add Huruikagi\u002Fspecbind --skill sb-contract-review",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Huruikagi\u002Fspecbind --skill sb-contract-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-contract-review\u002FSKILL.md",true,[],[46,52,57,64,71,78],{"skillNo":47,"name":48,"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":49,"categories":50,"keywords":51,"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":53,"name":48,"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":54,"categories":55,"keywords":56,"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":58,"name":59,"nameZh":6,"description":60,"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},"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":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},"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":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},"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":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},"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",[],[]]