Individual skill
spk-run-next
Drive the canonical spec-kitty next control loop and route query, step, blocked, decision_required, and terminal results.
src/charter/offering/skills/spk-run-next/SKILL.md
Source commit 25b7cd4fbc8f42ec71219408e2b5d76e7dae38b4
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,717
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- gemini-cli Repository topic
- spec-driven-development Repository topic
- cursor-agent Repository topic
- github-copilot Repository topic
- windsurf Repository topic
- ai-coding-workflow Repository topic
- ai-development-dashboard Repository topic
- ai-progress-tracking Repository topic
- coding-agent-orchestration Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 963 bytes
Read excerpt
# 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.