Skill Claude CodeCodex
Map Spec Kitty slash commands and CLI entry points to spk skills. Use when choosing /spec-kitty. commands or explaining command-skill boundaries.
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
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.
This repository also configures its own agents. See what spec-kitty tells them →
▶ Using Spec-Kitty for agentic coding of a Rust Complier CLI Robert Douglass · about Priivacy-ai/spec-kitty · on YouTube → Skill Claude CodeCodex
Map Spec Kitty slash commands and CLI entry points to spk skills. Use when choosing /spec-kitty. commands or explaining command-skill boundaries.
Skill Claude CodeCodex
Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective.
Skill Claude CodeCodex
Start here for Spec Kitty. Orient CLI users and supported agent-harness users; choose the right command, skill family, and recovery path.
Skill Claude CodeCodex
Handle Spec Kitty team authentication, hosted credentials, account selection, and auth-related recovery.
Skill Claude CodeCodex
Operate Spec Kitty connector integrations and route connector work across tracker, sync, SaaS, and external services.
Skill Claude CodeCodex
Operate Spec Kitty tracker sync (sync pull/sync push/sync run for local providers) and hosted SaaS-backed mission data.
Skill Claude CodeCodex
Operate Spec Kitty tracker workflows, tracker service discovery, binding, hosted routing, and tracker recovery.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: