sb-contract-review

Review milestone contract graphs for coherence across all persistent seams.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Huruikagi/pc-build-planner --skill sb-contract-review-huruikagi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sb-contract-review
Source: https://github.com/Huruikagi/pc-build-planner/tree/main/.agents/skills/sb-contract-review
Command: npx skills add https://github.com/Huruikagi/pc-build-planner --skill sb-contract-review-huruikagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a milestone changes some Specs in a specbind-managed project, untouched Specs and external consumers can silently break because nobody checks seams outside the changed scope. This Skill performs the single contract review that Tasks authoring waits on, judging whether every persistent seam in the project stays coherent against the milestone baseline. ## Core Features & Use Cases - Baseline diffing: Compares every current contract.yaml against the milestone baseline via Git, establishing exactly what changed before judging. - Whole-graph judgment: Reads every Contract in the project, not just participants, and checks scoped behavior for missing seams even when a Contract diff is empty. - Bounded remediation: Allows at most two remediation rounds with explicit user-confirmed gate invalidation, routing findings to the owning phase (sb-plan, sb-discovery) instead of editing other phases' artifacts. - Use Case: After design approval of a milestone touching checkout and billing Specs, run this review to confirm the shipping Spec's unchanged Contract still satisfies its consumers, then accept the review so Tasks authoring can proceed. ## Quick Start Use sb-contract-review to review the active milestone contract graph and accept it if all seams are coherent.

Frequently Asked Questions about sb-contract-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a milestone contract graph with specbind?▼

Run specbind milestone review status, scope, and check contracts, then diff every Spec's contract.yaml against the milestone baseline using git show. Present the assessment and accept with specbind milestone review accept --candidate - passing strict JSON on stdin.

What does the contract review check beyond changed Specs?▼

It reads every current Contract in the project, not only participants, because untouched Specs are the consumers most likely to break. It also checks scoped behavior for missing persistent seams even when a Contract diff is empty.

When is a contract review not required for a milestone?▼

A Direct-only milestone without shared agreement changes reports Status: not_applicable from specbind milestone review status. In that case the review is not required and the workflow stops without accepting any artifact.

Can the contract review edit contracts or invalidate gates itself?▼

No. It authors no Spec artifact and never edits another Spec's contract. Gate invalidation happens only after presenting the complete rewind cost and obtaining explicit user confirmation, with the owning phase performing the repair.

How many remediation rounds does the contract review allow?▼

At most two remediation rounds. After that, affected Specs stay in design, no artifact is written, and the unresolved findings are reported to the user.

What goes into deepInputs when accepting a contract review?▼

Only canonical requirements or design artifact selectors the judgment actually relied on, prefixed as specs/<spec>#<selector>. Every declared input is fingerprinted, so editing it later makes the review stale and blocks downstream gates.