Orchestrate multi-repo, multi-mission Spec Kitty programs across dependencies, parallel agents, review gates, merge, and post-merge closeout.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Priivacy-ai/spec-kitty --skill spk-run-program-orchestrate --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Spk Run Program Orchestrate?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/priivacy-ai-spk-run-program-orchestrate)More formats (shields.io, HTML) on the badges page.
---
name: spk-run-program-orchestrate
description: "Orchestrate multi-repo, multi-mission Spec Kitty programs across dependencies, parallel agents, review gates, merge, and post-merge closeout."
---
# 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.
## Legacy Alias
For detailed program orchestration mechanics, use
`spec-kitty-program-orchestrate` 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', ...
