What problem does it solve?
Spec Kitty workflows can stall when commands like next, review, accept, merge, sync, or dashboard report blockers such as missing artifacts, failed guards, stale worktrees, or decision-required loops. This Skill provides a structured recovery procedure so you can classify the blocker, apply one targeted repair, and resume the workflow without bypassing safety guards.
Core Features & Use Cases
- Blocker Classification: Categorizes failures into missing artifact, invalid state, guard failure, worktree/git issue, sync issue, auth issue, or user decision required.
- Guided Repair Loop: Directs you to the nearest specialist skill (setup doctor, git workflow, team sync, review, accept, or merge), applies one repair, then reruns the same command to compare output.
- Guard Preservation: Enforces the rule of resolving the reason a guard exists rather than bypassing it, escalating to the user only for product decisions or external credentials.
- Use Case: When
spec-kitty next reports a stale worktree blocker, use this Skill to classify it as a worktree/git issue, route to the git workflow specialist, fix the worktree, and rerun the command to confirm recovery.
Quick Start
Use the spk-run-blocked-recovery skill to diagnose why my spec-kitty next command is blocked and guide me through one repair step.
