Installation Guide
Spec Kitty is inspired by GitHub's Spec Kit. Installation commands below target the spec-kitty distribution while crediting the original project.
📖 Looking for the complete workflow? See the README: Getting Started guide for the full lifecycle from CLI installation through feature development and merging.
Prerequisites
- Linux/macOS (or Windows; PowerShell scripts now supported without WSL)
- AI coding agent: Claude Code, GitHub Copilot, or Gemini CLI
- Python 3.11+
- Git
- pipx for the recommended CLI install path
- Optional: uv if your team standardizes on uv-managed tools
Installation
Install Spec Kitty CLI
From PyPI (Recommended - Stable Releases)
Using pipx (preferred):
pipx install spec-kitty-cli
pipx installs Spec Kitty as an application in an isolated virtual environment
and places the spec-kitty command on your PATH. This is the safest default on
modern Python installations because many Linux distributions now block direct
system-wide pip install commands with PEP 668
externally-managed-environment errors.
If this is your first pipx install, make sure its binary directory is on your
PATH:
pipx ensurepath
Then open a new shell and verify:
spec-kitty --version
Using uv:
uv tool install spec-kitty-cli
Using pip in an activated virtual environment or managed CI Python image:
python -m pip install spec-kitty-cli
Use pip when you are already inside a project-specific virtual environment,
CI image, or other Python environment you intentionally manage. Avoid direct
system-wide pip install spec-kitty-cli on distro-managed Python installs.
From GitHub (Latest Development)
Use the GitHub install path when you need the latest unreleased code from
main.
Using pipx (preferred):
pipx install git+https://github.com/Priivacy-ai/spec-kitty.git
Using uv:
uv tool install spec-kitty-cli --from git+https://github.com/Priivacy-ai/spec-kitty.git
Using pip in an activated virtual environment or managed CI Python image:
python -m pip install git+https://github.com/Priivacy-ai/spec-kitty.git
Initialize a New Project
After installation, initialize a new project:
If installed with pipx, uv, or an active virtual environment:
spec-kitty init <PROJECT_NAME>
One-time usage (without installing):
Using pipx:
pipx run spec-kitty-cli init <PROJECT_NAME>
Using uvx:
uvx spec-kitty-cli init <PROJECT_NAME>
Add to an Existing Project
To add Spec Kitty to an existing repository, run init from that repository root:
cd /path/to/existing-project
spec-kitty init . --ai claude
What this does today:
- Creates the
.kittify/scaffold in the current directory - Adds the selected agent command directories
- Updates ignore files such as
.gitignore/.claudeignore - Leaves your Git history untouched;
initdoes not initialize Git or create commits
Best practices for existing projects:
- Commit or stash your current work before adding Spec Kitty.
- Review
.gitignoreafter init so agent directories remain untracked. - Use
spec-kitty verify-setup --diagnosticsif you want a post-install health check. - Start the workflow with
/spec-kitty.specify; mission selection happens there, not duringinit.
Choose AI Agent
You can proactively specify your AI agent during initialization:
spec-kitty init <project_name> --ai claude
spec-kitty init <project_name> --ai gemini
spec-kitty init <project_name> --ai codex
spec-kitty init <project_name> --ai claude,codex
Managing Agents After Initialization
After running spec-kitty init, you can add or remove agents at any time using the spec-kitty agent config command family.
To manage agents post-init:
- Add agents:
spec-kitty agent config add <agents> - Remove agents:
spec-kitty agent config remove <agents> - Check status:
spec-kitty agent config status
See Managing AI Agents for complete documentation on agent management workflows.
Non-Interactive Setup
For CI or scripts, use the non-interactive mode documented by spec-kitty init --help:
spec-kitty init <project_name> --ai claude --non-interactive
Verification
After initialization, you should see the following commands available in your AI agent:
/spec-kitty.specify- Create specifications/spec-kitty.plan- Generate implementation plans/spec-kitty.research- Scaffold mission-specific research artifacts (Phase 0)/spec-kitty.tasks- Break down into actionable tasks
Run spec-kitty dashboard --open if you want the live dashboard immediately after setup.
Troubleshooting
pip install fails with externally-managed-environment
On Ubuntu 24.04, Debian 12, Fedora, and other modern distributions, Python may
refuse direct system-wide pip install spec-kitty-cli commands because the OS
owns the system Python environment. Install the CLI with pipx instead:
pipx install spec-kitty-cli
pipx ensurepath
If you must use pip, create and activate a virtual environment first:
python -m venv .venv
source .venv/bin/activate
python -m pip install spec-kitty-cli
Git Credential Manager on Linux
If you're having issues with Git authentication on Linux, you can install Git Credential Manager:
#!/usr/bin/env bash
set -e
echo "Downloading Git Credential Manager v2.6.1..."
wget https://github.com/git-ecosystem/git-credential-manager/releases/download/v2.6.1/gcm-linux_amd64.2.6.1.deb
echo "Installing Git Credential Manager..."
sudo dpkg -i gcm-linux_amd64.2.6.1.deb
echo "Configuring Git to use GCM..."
git config --global credential.helper manager
echo "Cleaning up..."
rm gcm-linux_amd64.2.6.1.deb