Spec Kitty 3.2
Spec Kitty 3.2 documentation
Install the CLI, run missions through your AI harness, and keep specs, plans, work packages, and review evidence aligned.
Spec Kitty 3.2 is the current documentation set. Use it when you are installing Spec Kitty for the first time, upgrading an existing project, running missions through an AI harness, or checking exact CLI behavior.
Answer summary
- Current target version: Spec Kitty 3.2.
- Current runtime model: Charter-era missions with governed context injection.
- Current governance source:
.kittify/charter/charter.md. - Current mission loop:
spec-kitty next --agent <name> --mission <slug>. - Upgrade path: start at Migration to Spec Kitty 3.2, then follow the current install and project upgrade guides.
Choose your path
Tutorial
New to Spec Kitty
Install the CLI, initialize a project, and run your first mission with a guided outcome.
How-to
Upgrading to 3.2
Upgrade the CLI, refresh project files, and use migration notes only when older behavior matters.
How-to
Run in your harness
Use Claude Code, Codex, OpenCode, Cursor, Gemini, Pi TUI, and other supported hosts.
Reference
Look up commands
Find CLI commands, generated files, configuration, environment variables, and supported harnesses.
Divio documentation types
The current docs keep the four Divio types separate so you can choose by intent:
| Need | Use | Good first page |
|---|---|---|
| Learn by completing a guided flow | Tutorials | Getting Started |
| Complete a specific task | How-To Guides | Install on macOS |
| Look up exact behavior | Reference | CLI Commands |
| Understand why the system works this way | Explanation | Mission System |
Current 3.2 surface
- 3.2 current overview explains the current Charter-era model.
- Install and upgrade guides are the source of truth for current project files.
- Supported harnesses shows the host support matrix.
- Slash commands maps host command files to Spec Kitty actions.
- Environment variables covers CI, sync, and local runtime switches.
Migration and archive
Use migration pages when moving an existing project into 3.2. They are not the current learning path.
1.x and 2.x docs are preserved as historical archive. They should not be used to start a new 3.2 project.