sb-release

Orchestrates milestone release by binding versions, running release adapters, and finalizing SpecBind state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Closing a milestone involves many error-prone steps: binding the correct version, running the project's release procedure, verifying the publication actually happened, and finalizing milestone metadata. This Skill orchestrates that entire workflow through the SpecBind CLI so nothing is skipped, invented, or partially done. ## Core Features & Use Cases - Version binding with safeguards: Runs release preflight, asks the user for the exact version label (never inventing or normalizing one), and binds it to the active Roadmap with evidence-preserving semantics. - Release adapter orchestration: Reads the project's Release and Git adapters, bootstraps an unconfigured adapter from repository evidence, and executes Prepare, Publish, Verify, and After-finalize guidance with explicit user confirmation before publishing. - Verification and finalization: Treats publication as a completion claim requiring fresh external evidence, writes per-Spec summaries, finalizes via specbind release finalize, and checkpoints only the finalized lifecycle metadata. - Use Case: After completing all Specs in a milestone, invoke this Skill to bind v1.4.0, follow the project's documented release procedure, verify the tag or package exists externally, and close the milestone with a clean audit trail. ## Quick Start Ask the assistant to use the sb-release skill to release and finalize the currently active milestone.

Frequently Asked Questions about sb-release

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

FAQPage Schema
How do I release and finalize a SpecBind milestone?▼

Run the sb-release workflow: it reads milestone status and release adapters, binds a user-supplied version, executes the project's Prepare/Publish/Verify steps, then finalizes with per-Spec summaries via specbind release finalize. The whole milestone is released or nothing is.

What happens if the Release adapter is not configured?▼

The workflow enters a bootstrap flow that inspects repository evidence such as release workflows, manifests, and RELEASE documentation, then drafts a complete replacement adapter. After explicit approval and a narrow checkpoint, the run stops without performing any release steps.

Can the skill choose or normalize a release version automatically?▼

No. The version label is opaque and case-sensitive, so the skill always asks the user and never invents or normalizes one. For example, v1.4.0 and 1.4.0 are treated as different releases, and rebinding requires explicit confirmation with --rebind.

Does SpecBind verify that a publication actually happened?▼

No. SpecBind never verifies external publication; the skill and user judge that with fresh evidence such as reaching the published artifact. Re-reading the publish command's own success output does not count as verification.

What happens when publish succeeds but verification fails?▼

The milestone stays active and all SpecBind artifacts remain unchanged. The skill does not roll back the publication or blindly retry, since publish steps may not be idempotent; it reports the state and works with the user on reconciling or retrying.

Does the release workflow push commits or tags to remotes?▼

Only when the user explicitly requests it for the current run or a project instruction independently requires it. Publication approval alone does not authorize pushing, and the skill never amends, force-pushes, or moves published tags.