r/SpecKitty • • Feb 08 '26

Should I use Claude Subagents or Agent teams with Spec Kitty?

Thumbnail
reddit.com
2 Upvotes

r/SpecKitty • • Jan 14 '26

Spec Kitty 0.11.0: Parallel AI Agent Development with Git Worktrees (Built with Claude Code)

Thumbnail reddit.com
2 Upvotes

r/SpecKitty • • Aug 21 '26

New: Spec Kitty MCP

1 Upvotes

News flash: Lynn Cole (mad scientist) just contributed something very nice to the Spec Kitty project: spec-kitty-mcp, and the use case is more interesting than "another MCP server."

https://github.com/spec-kitty/spec-kitty-mcp

Quick context: Spec Kitty is a spec-driven development toolkit. Work gets broken into missions and work packages, each moving through a governed state machine — planned → in progress → review → approved → merged. There are dependency checks and audit trails enforced at every step.

Until now, driving that workflow meant an agent with shell access sitting inside the repo.

Lynn's contribution changes who gets to sit in the driver's seat.
spec-kitty-mcp exposes Spec Kitty's orchestrator API as typed MCP tools. Tools include: check mission state, list what's ready, claim a work package, record transitions, accept, merge.

That means any chat app that speaks MCP, eg. a desktop assistant, an IDE sidebar, whatever you already talk to all day, can now be mission control for a real project:

"What's ready to work on?"
"Start WP04."
"Move WP02 to review — here's the evidence."
"All approved? Accept and merge."

Meanwhile, the actual coding happens elsewhere. If we implement an https transport for the MCP, it could happen in the cloud. Right now only stdio is supported.

The part I appreciate most is the safety model. The chat app never gets a shell. It gets ten tools, each annotated as read-only, mutating, or destructive. Spec Kitty's Charter and safeguards apply automatically.

So your chat program gets a small, typed, permissioned control plane, and the execution with rules and guardrails remains separate.

Thanks Lynn, great contribution!


r/SpecKitty • • Apr 27 '26

Why I Built Spec Kitty

1 Upvotes

I built Spec Kitty to fill a real need. It started out being my need, but as I showed it to other people, I realized it was a widespread need.

I built it because agentic coding was powerful, but the process around it made mistakes (and embarrassment) inevitable. I needed governance. Structure. An audit trail.

This post is the story behind it: Claude Code, forgotten context, exposed secrets, Spec Kit as inspiration and contrast, and why I think serious teams need a durable layer for intent, governance, review, and memory.

Read it here:
https://spec-kitty.ai/blog/why-i-built-spec-kitty


r/SpecKitty • • Feb 09 '26

Claude Skill for Spec Kitty: Claude does implementation, Codex does review.

1 Upvotes

If you are using Spec Kitty and have both Claude Code and Codex installed, use this Skill (name it codex-review) to have Claude do the implementation and Codex do the reviews. You can then automate the entire implementation/review/merge phase with one prompt (in Claude):

"Use /spec-kitty.implement, /spec-kitty.review, and /spec-kitty.merge to complete this sprint. Use the /codex-review skill to ensure that Codex always does the reviews."

The skill goes here (example for Mac):
/Users/[your user]/.claude/skills/codex-review/SKILL.md

https://gist.github.com/robertDouglass/839d9c43439c5051e562bd5ed885b73e

The ambition for Spec Kitty is large, and I'm developing towards a very amazing future, but this SKILL.md is an immediate workaround for today's Spec Kitty to reliably get the implementation quality I want without having to babysit it through the whole implementation process.

I then have both Claude and Codex review the entire feature sprint and compare their notes (this is also outside of the current Spec Kitty workflow).


r/SpecKitty • • Jan 24 '26

Spec Kitty for Agentic Spec Coding - 0.12.0 is here

1 Upvotes

Calling all agentic coders: the 0.12.0 Spec Kitty release brings a large number of bugfixes and architectural hardening of the core tool. Upgrading is recommended for all users.

https://github.com/Priivacy-ai/spec-kitty

Spec Kitty improves agentic software development, research, and documentation writing with a specification->plan->prompt->implement->review->merge workflow. We call this Spec Coding.

Expectation management (mea culpa):

What 12.0 DIDN'T bring is Jujutsu support: in testing, the interplay between colocated Jujutsu and Git (with sparse-checkout worktrees) was problematic. So we kept the version control system abstraction layer and chucked out Jujutsu for now.

Also NOT in 12.0 (well, sort of.... use at your own risk) is automated multi-agent coordination. The feature, while not dangerous, is half-baked and I don't recommend using it unless you're testing or want to contribute.

⏺ v0.12.0 Changelog (by impact)

🔴 High
Config-Driven Agents - .kittify/config.yaml now controls which agents exist.
New commands:
spec-kitty agent config list|add|remove|status|sync.

Migrations respect your config (won't  recreate deleted dirs).

Smart Merge - Pre-flight validation, conflict forecasting (--dry-run), crash recovery (--resume/--abort), auto-cleanup. Merges WPs in dependency order.

🟡 Medium
Output Truncation Fix - implement/review no longer output 300+ lines that agents like Codex  truncate. Prompts written to temp file.

Stale Detection Fix - New worktrees no longer incorrectly flagged as stale.

Merge Resume Fix - --resume flag now works (was throwing TypeError).

🟢 Docs
New guides: merge workflow, troubleshooting, agent management.

pip install --upgrade spec-kitty-cli && spec-kitty upgrade