skills.rest
Priivacy-ai
Priivacy-aiOFFICIAL
Explore all skills by this author →
GitHub

spec-kitty-program-orchestrate

Orchestrates multi-repo Spec Kitty missions through specify, plan, implement, review, and merge phases.

1.6k|156|Updated Oct 9, 2025
Search Tags:#spec-kitty#mission review#sub-agent dispatch#spec-Driven Development#Workflow Automation#Git Worktrees#multi-repo orchestration
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spec-kitty-program-orchestrate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-kitty-program-orchestrate
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spec-kitty-program-orchestrate
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spec-kitty-program-orchestrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating a feature release that spans multiple repositories is error-prone: repos must ship in dependency order, parallel sub-agents can silently stall, and post-merge reviews and remediations are easy to skip. This Skill drives the entire cross-repo program from kickoff to final merge without requiring the user to hand-hold every transition.

Core Features & Use Cases

  • Ordered multi-repo execution: Runs the full specify → plan → tasks → implement → review → merge → mission-review → remediation pipeline per repo, respecting cross-repo contract dependencies.
  • Parallel sub-agent dispatch: Dispatches implementer and reviewer sub-agents per work package, capped at ~6 concurrent agents, with cross-repo context injected into every prompt.
  • Pulse heartbeat safety net: Keeps a scheduled wakeup armed during uninterrupted runs to detect dead or stalled sub-agents and recover automatically.
  • Known-friction workarounds: Ships ready-made fixes for test-DB collisions, stale-lane merges, and post-merge invariant-check failures.
  • Use Case: A team shipping "Decision Moment V1" across an events repo, a SaaS backend, a CLI, and a web app uses this Skill to sequence the repos, run missions in parallel where dependencies allow, and land all merges plus mission reviews autonomously.

Quick Start

Ask the agent to orchestrate the full Spec Kitty mission workflow across your ordered list of repositories, for example: "Ship this program across repos A, B, and C in dependency order, working uninterrupted."

Frequently Asked Questions about spec-kitty-program-orchestrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate a multi-repo release with Spec Kitty?▼

Provide an ordered list of repos with their issue numbers and cross-repo dependencies, then authorize the autonomy scope. The orchestrator runs specify, plan, tasks, implement-review, merge, mission review, and remediation phases per repo in dependency order.

How do I run parallel sub-agents for Spec Kitty work packages?▼

Dispatch one implementer sub-agent per unblocked work package and separate reviewer sub-agents, capping concurrency at about six agents. Include cross-repo contract references and known friction workarounds in every dispatch prompt.

When should I not use multi-repo program orchestration?▼

Skip it when there is only one mission, when repos are fully independent with no ordering or contract dependencies, or when the user wants manual control over every dispatch. Use the single-mission implement-review skill instead.

Why do Spec Kitty merges fail with stale lane errors?▼

Stale-lane errors occur when multiple work packages touched shared files like pyproject.toml or urls.py. Merge the mission branch into each stale lane worktree, resolve conflicts, commit, then retry the outer merge.

How do I prevent silent stalls during long autonomous agent runs?▼

Keep a scheduled wakeup armed every 20-30 minutes as a pulse heartbeat. On each fire, list running tasks, peek at agent output, check mission status for stuck work packages, and dispatch repair agents if anything is stalled.

Why does moving work packages to done fail after a merge?▼

The post-merge invariant check fails because the .worktrees directory is untracked. Temporarily move .worktrees aside, run the move-task commands for each work package, then restore the directory.

Related Skills

Explore More Software Engineering Skills→
FaysilAlshareefFaysilAlshareef
4

multi-repo-workflow

Coordinate cross-repo changes and deployments across microservice repositories.

Community
Advanced
johnrtiptonjohnrtipton
4

pipeline-retro

Automates milestone retrospectives by collecting inputs from PRs, GitHub issues, and retro documents.

Community
Intermediate
kimprobablykimprobably

spec-kitty-mission-review

Trace merged Spec Kitty mission implementations from spec artifacts to tests and code diffs.

Community
Advanced
danmartinez78danmartinez78

shadowhound-platform

Document architecture, repositories, and agent API context for the ShadowHound SAR platform.

Community
Advanced