sb-steering

Create and synchronize durable project steering documents via the SpecBind CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-lived project guidance (how the project is built, what it values, which constraints every change inherits) drifts out of date as code evolves, and stale steering misroutes real work. This Skill bootstraps, synchronizes, and extends steering documents so they stay accurate. ## Core Features & Use Cases - Bootstrap steering: Dispatch fresh readers to analyze product, technology, and structure, then author the first steering document set from SpecBind templates. - Synchronize after code changes: Compare existing steering against the current codebase, revise contradicted statements in place, and report drift you did not act on. - Add subject documents: Document a single durable convention (testing, API, security, deployment) with a unique kebab-case artifact identity, verified via specbind steering list and specbind steering check. - Use Case: After a major refactor, ask the agent to synchronize project steering; it reads the existing collection through the SpecBind CLI, dispatches codebase readers, updates only what the code demonstrably contradicts, and commits the verified changes per the Git adapter. ## Quick Start Ask the agent to bootstrap or synchronize this project's steering documents using the sb-steering workflow.

Frequently Asked Questions about sb-steering

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

FAQPage Schema
How do I create project steering documents with SpecBind?▼

Run specbind steering list to see what exists, dispatch readers to analyze product, technology, and structure, then materialize documents from templates via specbind template read steering. Verify each document appears in specbind steering list before finishing.

How do I update steering docs after code changes?▼

Use the synchronize workflow: read existing steering through the CLI, have readers compare it against the codebase, and revise in place only what the code demonstrably contradicts. Report drift you did not act on rather than rewriting sound documents.

Can I read steering files directly instead of using the CLI?▼

No. The skill forbids reading or globbing the steering directory directly; all access goes through specbind steering list and specbind steering read. Direct file reads are allowed only to repair a malformed document named by a diagnostic.

What happens if two steering documents share the same identity?▼

A duplicate identity is a hard discovery error that drops both documents from the collection. Inspect Git history to determine which file is the newly introduced duplicate, and without provenance present all paths to the maintainer instead of choosing one yourself.

When should I not add a new steering document?▼

Do not add a document when the project has no settled convention for the subject. Report the absence, ask the maintainer for the actual convention or an explicit decision, and stop before creating a file rather than inventing policy.