Drive the canonical spec-kitty next control loop and route query, step, blocked, decision_required, and terminal results.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add Priivacy-ai/spec-kitty --skill spk-run-next --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Spk Run Next?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/priivacy-ai-spk-run-next)More formats (shields.io, HTML) on the badges page.
---
name: spk-run-next
description: "Drive the canonical spec-kitty next control loop and route query, step, blocked, decision_required, and terminal results."
---
# spk-run-next
Use this skill when advancing an active mission, asking what to do next, or
recovering from a runtime decision.
## Flow
1. Query state with `spec-kitty next --mission <handle> --json` or advance with
`spec-kitty next --agent <name> --mission <handle> --result <success|failed|blocked>`.
2. Read the returned decision kind.
3. For `query`, inspect only; do not execute a prompt or mark a result.
4. For `step`, execute the generated prompt file.
5. For `decision_required`, answer with `--answer`, `--result`, `--agent`, and
`--decision-id` when multiple decisions are pending.
6. For `blocked`, fix guard failures before retrying.
7. For `terminal`, route to `spk-gate-accept`.
## Legacy Alias
For detailed runtime semantics, use `spec-kitty-runtime-next` when available.
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', ...