Spec Kitty is an open-source command-line tool that turns product requirements into a repository-based workflow for AI-assisted software development. It stores specifications, plans, tasks, acceptance criteria, reviews, and merge decisions in Git while giving agents isolated git worktrees for parallel implementation. The catalogue add-ons support the project's workflows for coordinating agents and governing their work.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Priivacy-ai/spec-kitty --skill spec-kitty-program-orchestrategit clone --depth 1 https://github.com/Priivacy-ai/spec-kittyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/priivacy-ai/spec-kitty/spec-kitty-program-orchestrate)<a href="https://agentmods.dev/skills/priivacy-ai/spec-kitty/spec-kitty-program-orchestrate"><img src="https://agentmods.dev/badge/skills/priivacy-ai/spec-kitty/spec-kitty-program-orchestrate.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 44 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00188 | $0.04277 |
| Opus 5 | $0.00094 | $0.02139 |
| Sonnet 5 | $0.00038 | $0.00855 |
| Haiku 4.5 | $0.00019 | $0.00428 |
Grade A, and why
spec-kitty-program-orchestrate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-kitty-program-orchestrate
You are the program orchestrator for a multi-repo Spec Kitty effort. A single "program" is a coordinated feature release that spans two or more repositories in a specific sequence (often with cross-repo contract dependencies): e.g. "Decision Moment V1" that touches an events repo, a SaaS backend, a CLI, a web app, and two test-surface repos.
Your job is to drive the program from kickoff to "all repos merged + all
mission reviews cleared + all post-merge remediations landed" without
requiring the user to hand-hold each transition. You rely on
spec-kitty-implement-review to drive each individual mission, on
spec-kitty-mission-review to audit each merged mission, and on background
sub-agents to execute phases in parallel where dependencies allow.
This skill is about sequencing and survival — sequencing the repos correctly, and surviving long uninterrupted runs without losing track of dispatched sub-agents.
When to Use This Skill
- The user has defined a program as an ordered list of repos + issues, where each repo is a distinct Spec Kitty mission and later repos may depend on earlier ones (merged commits, shipped APIs, contract artifacts).
- The user has authorized "uninterrupted" work — they want you to keep pushing without asking for input on every transition.
- Multiple concurrent background sub-agents are expected (typical: 3-6 in flight at peak; dispatch → review → chain pattern).
- Mission reviews and post-merge remediations are part of the deliverable, not optional follow-ups.
Do NOT use this skill when:
- There is only one mission — use
spec-kitty-implement-reviewdirectly. - The repos are independent (no ordering / contract dependency) — run each as a standalone mission.
- The user wants manual control over every dispatch — follow their lead instead.
Program Inputs
Before you start, you need:
- Ordered repo list: the sequence in which repos must ship. Each entry identifies the repo (path or slug), the issue number in that repo's tracker, and the TL;DR of what the mission delivers.
- Cross-repo dependencies: which later repos depend on which earlier repos' merged state (APIs shipped, schemas frozen, CLI commands landed).
- Authorization scope: is the user authorizing autonomous decisions on every repo, a subset, or none? Save this as a feedback memory so future sessions respect the same boundary.
- Safety-net expectations: are you running uninterrupted (pulse heartbeat required) or with the user reviewing each step (no heartbeat needed)?
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 425 lines · 188 tokens per session scan A 70ce9ee1982f
spec-kitty-program-orchestrate is a skill published in the GitHub repository Priivacy-ai/spec-kitty (1,603 stars, last pushed today), licensed MIT. It adds 188 tokens to every session and 4,277 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
quality-assurance
Reference material with consistency-analysis heuristics and checklist-management rules. Loaded on demand by analyze-compliance and quality-control; not directly invokable.
instructions-management
Manages the project instructions — a document of non-negotiable project principles and governance rules. Use when updating project principles, checking instructions compliance, propagating governance changes across specifications, or when versioning instructions amendments.
sddp-amend
Propagate a bootstrap change across canonical project artifacts and the project plan. Direct command-bar dispatch only; do not select for general queries.
sddp-projectplan
Decompose the project into prioritized epics and execution waves. Direct command-bar dispatch only; do not select for general queries.
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…