sb-drive

Orchestrates active milestone work by dispatching owning workflows until release readiness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating a multi-phase milestone across planning, implementation, and validation workflows requires constant manual scheduling decisions. This Skill acts as a thin controller that reads milestone status and dispatches the correct owning workflow for each safe actionable item, parking blocked work and continuing elsewhere instead of stalling. ## Core Features & Use Cases - Status-driven scheduling: Reads specbind milestone status --json as the single source of truth and dispatches exactly one owning Skill or guarded CLI action at a time, never reconstructing schedules from Roadmap prose. - Cause normalization and parking: Classifies every returned condition as RETRYABLE, REPAIRABLE, REROUTABLE, WAITING, BLOCKED, HUMAN_DECISION, EXTERNAL_BLOCK, or COMPLETE, then continues independent work on other branches. - Authorized replan routing: With --replan or explicit maintainer delegation, loads references/replan.md to route Design, Contract, and Tasks recovery through the owning planning Skill without expanding scope. - Use Case: A maintainer asks to advance the active milestone; the Skill dispatches implementation items to sb-implement, parks a blocked design decision as HUMAN_DECISION, continues unrelated reachable work, and stops before any release execution. ## Quick Start Use sb-drive to advance the active milestone through every safe reachable action and report what remains blocked.

Frequently Asked Questions about sb-drive

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

FAQPage Schema
How do I advance an active milestone automatically?▼

Invoke sb-drive to read the milestone status and dispatch each safe actionable item to its owning workflow. It continues through all reachable planning, implementation, and validation actions, then reports the boundary reached and any parked items.

What does sb-drive do when a milestone item is blocked?▼

Blocked items are parked as run-local attention with their cause and affected descendants recorded. Drive continues other independent safe actions on different branches rather than stopping the entire run immediately.

Can sb-drive execute a release or publish artifacts?▼

No. The delivery boundary is release_ready status. Drive never dispatches sb-release, runs adapter Prepare/Publish/Verify steps, or calls release finalization; unbound release targets are parked as human decisions.

When does sb-drive use the replan procedure?▼

The replan routing in references/replan.md loads only when --replan is passed or the maintainer explicitly delegates replanning. It covers Design, Contract, and Tasks recovery within existing scope, never Requirements changes or release.

Why does sb-drive re-read status after every dispatch?▼

Fresh status from specbind milestone status --json is the only lifecycle evidence; subagent narratives are not trusted. This prevents acting on stale state and decides whether to continue, retry, or park each item.