Recover from Spec Kitty blocked runtime states, missing artifacts, failed guards, stale worktrees, and decision-required loops.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Priivacy-ai/spec-kitty --skill spk-run-blocked-recovery --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Spk Run Blocked Recovery?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/priivacy-ai-spk-run-blocked-recovery)More formats (shields.io, HTML) on the badges page.
---
name: spk-run-blocked-recovery
description: "Recover from Spec Kitty blocked runtime states, missing artifacts, failed guards, stale worktrees, and decision-required loops."
---
# spk-run-blocked-recovery
Use this skill when `next`, review, accept, merge, sync, or dashboard output
shows a blocker.
## Flow
1. Capture the exact command and blocker output.
2. Classify the blocker: missing artifact, invalid state, guard failure,
worktree/git issue, sync issue, auth issue, or user decision required.
3. Use the nearest specialist skill: setup doctor, git workflow, team sync,
review, accept, or merge.
4. Make one repair, rerun the same command, and compare output.
5. Escalate to the user only when the command requires a product decision or
external credential.
## Rule
Do not bypass a guard. Resolve the reason the guard exists.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
