Spec Kitty

Spec Kitty Spec-driven development for AI coding agents, multi-agent workflows, and governed software factories.

Spec Kitty is an open-source CLI for turning product intent into a repo-native AI coding workflow:

spec -> plan -> tasks -> next -> review -> accept -> merge

Use it to build a governed software factory around Claude Code, Codex, Cursor, Gemini, GitHub Copilot, Windsurf, OpenCode, and other AI coding agents. Spec Kitty keeps specs, plans, work packages, acceptance criteria, review state, and merge decisions in your repository, then gives agents isolated git worktrees so implementation can happen in parallel without branch chaos.

Team Kitty 4.x prerelease

main carries the 4.x release-candidate line. To test RC2, install its exact version:

uv tool install 'spec-kitty-cli==4.0.0rc2'

This prerelease is for qualification; stable launch acceptance remains pending. Normal stable installs continue to select the published stable release.

Bright Software Factory, Not a Black Box

Spec Kitty is for teams building software factories: repeatable inputs, clear work-package boundaries, isolated execution, visible progress, and review gates. It can support dark software factories and autonomous coding experiments, but it is deliberately not a lights-out black box by default. Humans define intent, architecture, and acceptance criteria; agents implement inside traceable worktrees; reviewers accept, reject, or merge with an audit trail.

The goal is not more prompt text. The goal is a durable operating system for agentic coding where the repository remains the source of truth.

Is It For You?

Use Spec Kitty when:

• AI coding sessions are losing requirements, decisions, or acceptance criteria.
• You want specs, plans, tasks, reviews, and merge state stored in Git.
• Multiple agents or developers need clear work-package boundaries.
• You are running parallel Claude Code, Codex, Cursor, Copilot, Gemini, or Windsurf work and need git worktree isolation.
• You are moving from vibe coding to a repeatable spec-driven development workflow.
• You want a local workflow first, with optional hosted tracker and sync integrations later.

It is probably overkill for one-off edits, tiny scripts, or teams that do not use Git.

What It Provides

Need	Spec Kitty provides
Start from intent	Guided specify, plan, and tasks workflows
Keep agents aligned	Repository-native mission artifacts under kitty-specs/
Split implementation	Work packages with lifecycle lanes such as planned, in_progress, for_review, approved, and done
Run agents in parallel	Isolated git worktrees under .worktrees/
Keep quality visible	Review, accept, merge, and retrospective gates
See progress	Lane-by-lane mission status with spec-kitty agent tasks status (--json for tools)
Integrate agents	Slash commands or skills for Claude Code, Codex, Cursor, Gemini, Copilot, Windsurf, OpenCode, and more
Learn from missions	Every completed mission generates a retrospective by default. Tune via .kittify/config.yaml#retrospective or charter; see how-to.

Common Use Cases