← ClaudeAtlas

sb-planlisted

Plan active Spec work through Requirements, Design, Contract Review, and Tasks, or run one explicitly requested planning phase for one named Spec. Ordinary planning uses one named Spec or explicit all-Spec scope.
Huruikagi/specbind · ★ 3 · Code & Development · score 72
Install: claude install-skill Huruikagi/specbind
# Plan active Spec work For a Drive recovery dispatch carrying explicit `--replan` authority and named affected Specs, read [Replan during Drive](references/replan.md) first. That procedure owns the recovery scope and overrides the ordinary no-rewind delegation rule only for Design and Tasks. Do not repeat the scope or delegation question already settled by that dispatch. Ordinary Plan requests use the following entry rules unchanged. ## First action: fail closed on an unspecified scope Classify the maintainer's request **before reading phase procedures, Spec artifacts, templates, protocols, Steering, or implementation**. For a request such as "plan the active work" that names neither one Spec nor all Specs, the only workflow reads permitted are the language-style Rule below and `specbind milestone status`. Then name every available Spec choice, also name the all-Spec choice, ask the maintainer to select one, and stop. An `Actionable` item, a single participating Spec, or an obvious next phase is not scope authorization. Do not run `specbind spec status`, select a phase reference, investigate missing artifact details, or dispatch a phase until the maintainer chooses named or all-Spec scope. This first-action guard takes precedence over every later routing and scheduling instruction. ## Apply project language style Before authoring orchestration or user-facing prose, read: ```sh specbind rule read language-style --for consume ``` Apply returned policy only to natural-l