Individual skill
spk-run-program-orchestrate
Orchestrate multi-repo, multi-mission Spec Kitty programs across dependencies, parallel agents, review gates, merge, and post-merge closeout.
src/charter/offering/skills/spk-run-program-orchestrate/SKILL.md
Source commit 25b7cd4fbc8f42ec71219408e2b5d76e7dae38b4
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- 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 · 834 bytes
Read excerpt
# spk-run-program-orchestrate
Use this skill when a user wants to coordinate several related Spec Kitty
missions or repositories as one program.
## Flow
1. Build the mission dependency order before launching work.
2. Use `spk-run-next` for each mission's authoritative next action.
3. Coordinate parallel implementation only where dependencies allow.
4. Keep review, accept, merge, mission-review, and retrospective gates per
mission.
5. Surface blockers as program risks without bypassing mission-level gates.
