sb-debug

What problem does it solve? When a SpecBind workflow task fails or cannot be implemented, teams often guess at the cause or retry with the same flawed reasoning. This Skill performs a read-only investigation that establishes the true root cause, categorizes it, and routes it to the right owner instead of letting failed attempts repeat. ## Core Features & Use Cases - Structured diagnosis contract: Every run ends with a parseable block naming CATEGORY (IMPLEMENTATION, REVIEW, PLAN, ARTIFACT, ENVIRONMENT, or UNDETERMINED), CAUSE, NEXT_ACTION, and UNCERTAIN items. - Evidence-based investigation: Reads specs, tasks, contracts, designs, implementation notes, and steering documents via the specbind CLI to find where actual behavior first diverged from approved artifacts. - Read-only guarantee: Never modifies tracked files or applies the fix, preserving evidence for whoever implements the correction. - Use Case: A task in your milestone is blocked after two failed attempts. Dispatch this Skill in a fresh context with the failure details; it identifies that the design artifact contradicts the requirements (ARTIFACT category) and routes the fix back to planning instead of another doomed implementation attempt. ## Quick Start Ask the assistant to use sb-debug to diagnose why the current SpecBind task failed and return the categorized diagnosis.