sb-plan

Orchestrate Spec planning through Requirements, Design, Contract Review, and Tasks approval gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multi-phase specification planning across Requirements, Design, Contract Review, and Tasks is error-prone when scope, gate authority, and validation order are inferred rather than explicit. This Skill enforces a fail-closed orchestration route so every planning run has an explicit scope, authorized gates, and independent design validation before approval. ## Core Features & Use Cases - Complete planning route: Orchestrates one named Spec or all Specs through Requirements, Design, independent validation, global Contract Review, and Tasks approval via the specbind CLI. - Single-phase mode: Runs exactly one explicitly requested Requirements, Design, or Tasks phase for one named Spec without silently expanding scope. - Recovery and shared contracts: Handles Drive replan recovery with explicit rewind authority and prepares project shared Contracts for --shared scope. - Use Case: A maintainer asks to plan the active milestone; the Skill reads milestone status, asks for named or all-Spec scope, obtains gate delegation, dispatches phase receivers, and stops after Tasks approval with a full report. ## Quick Start Ask the assistant to use sb-plan to plan the active Spec work for a named Spec through its approval gates.

Frequently Asked Questions about sb-plan

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

FAQPage Schema
How do I plan a Spec through Requirements, Design, and Tasks approval?▼

Invoke sb-plan with either one named Spec or an explicit all-Spec scope. The Skill reads milestone status, obtains gate delegation, dispatches each phase receiver in order, runs independent design validation, and stops after Tasks approval.

How do I run only one planning phase like Design or Tasks?▼

Explicitly name both the Spec and the single phase you want authored, revised, or rerun. Single-phase mode reads only that phase's procedure reference and never expands to other Specs or silently continues to later phases.

Does sb-plan implement code or validate completion after planning?▼

No. The Skill stops after Tasks approval for ordinary milestones, or after Contract Review for reverse milestones. Implementation, completion validation, and releases are explicitly out of scope and belong to other workflows.

What happens when design validation returns NOT_READY?▼

A NOT_READY verdict blocks approval. The orchestrator keeps a blocking-finding ledger and allows at most two Design-owned revisions per Spec, with fresh independent validation required to account for every prior finding before approval.

Can sb-plan approve gates without user confirmation?▼

Only when the user explicitly delegates named gates for the presented scope in one confirmation. Delegated approvals record the workflow name in durable gate evidence; without explicit or delegated authority, the Skill presents results and stops.