{"id":35743769,"url":"https://github.com/priivacy-ai/spec-kitty","last_synced_at":"2026-05-28T07:04:06.624Z","repository":{"id":321281587,"uuid":"1072945981","full_name":"Priivacy-ai/spec-kitty","owner":"Priivacy-ai","description":"The AI Development Dashboard \u0026 Workflow Automation Platform for Spec-Driven Development. Real-time kanban tracking for multi-agent coding workflows with Claude, Cursor, Gemini, Codex and more.","archived":false,"fork":false,"pushed_at":"2026-01-16T19:03:24.000Z","size":11241,"stargazers_count":352,"open_issues_count":11,"forks_count":32,"subscribers_count":1,"default_branch":"main","last_synced_at":"2026-01-17T03:58:33.706Z","etag":null,"topics":["agentic-coding","ai-agents","ai-coding-workflow","ai-development-dashboard","ai-progress-tracking","claude-code","code-workflow","coding-agent-orchestration","cursor-agent","development-kanban","gemini-cli","github-copilot","kanban-workflow","multi-agent-support","real-time-tracking","spec-driven-development","spec-workflow-automation","structured-development","windsurf","worktree-strategy"],"latest_commit_sha":null,"homepage":"https://priivacy-ai.github.io/spec-kitty/","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Priivacy-ai.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":"AGENTS.md","dco":null,"cla":null}},"created_at":"2025-10-09T12:29:47.000Z","updated_at":"2026-01-16T20:46:12.000Z","dependencies_parsed_at":"2025-10-28T21:20:34.123Z","dependency_job_id":"ab7d25e4-1cd3-4e22-8c6c-d42aa9ac1bf1","html_url":"https://github.com/Priivacy-ai/spec-kitty","commit_stats":null,"previous_names":["priivacy-ai/spec-kitty"],"tags_count":142,"template":false,"template_full_name":null,"purl":"pkg:github/Priivacy-ai/spec-kitty","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Priivacy-ai%2Fspec-kitty","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Priivacy-ai%2Fspec-kitty/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Priivacy-ai%2Fspec-kitty/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Priivacy-ai%2Fspec-kitty/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Priivacy-ai","download_url":"https://codeload.github.com/Priivacy-ai/spec-kitty/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Priivacy-ai%2Fspec-kitty/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28698343,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-23T17:25:48.045Z","status":"ssl_error","status_checked_at":"2026-01-23T17:25:47.153Z","response_time":59,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["agentic-coding","ai-agents","ai-coding-workflow","ai-development-dashboard","ai-progress-tracking","claude-code","code-workflow","coding-agent-orchestration","cursor-agent","development-kanban","gemini-cli","github-copilot","kanban-workflow","multi-agent-support","real-time-tracking","spec-driven-development","spec-workflow-automation","structured-development","windsurf","worktree-strategy"],"created_at":"2026-01-06T16:21:17.652Z","updated_at":"2026-05-28T07:04:06.604Z","avatar_url":"https://github.com/Priivacy-ai.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"https://github.com/Priivacy-ai/spec-kitty/raw/main/media/logo_small.webp\" alt=\"Spec Kitty Logo\"/\u003e\n    \u003ch1\u003eSpec Kitty\u003c/h1\u003e\n    \u003cp\u003e\u003cstrong\u003eSpec-driven development for AI coding agents.\u003c/strong\u003e\u003c/p\u003e\n\u003c/div\u003e\n\nSpec Kitty is an open-source CLI for turning product intent into a repeatable agent workflow:\n\n```text\nspec -\u003e plan -\u003e tasks -\u003e next -\u003e review -\u003e accept -\u003e merge\n```\n\nIt keeps the important context in your repository, creates work packages that agents can execute, and uses git worktrees so implementation work can happen without constantly switching branches.\n\n[![PyPI version](https://img.shields.io/pypi/v/spec-kitty-cli?style=flat-square\u0026logo=pypi)](https://pypi.org/project/spec-kitty-cli/)\n[![License: MIT](https://img.shields.io/badge/license-MIT-yellow?style=flat-square)](LICENSE)\n[![Python 3.11+](https://img.shields.io/badge/python-3.11+-blue?style=flat-square)](https://www.python.org/downloads/)\n\n## Is It For You?\n\nUse Spec Kitty when:\n\n- AI coding sessions are losing requirements, decisions, or acceptance criteria.\n- You want specs, plans, tasks, reviews, and merge state stored in the repo.\n- Multiple agents or developers need clear work package boundaries.\n- You want a local workflow first, with optional hosted tracker and sync integrations later.\n\nIt is probably overkill for one-off edits, tiny scripts, or teams that do not use Git.\n\n## What It Provides\n\n| Need | Spec Kitty provides |\n| --- | --- |\n| Start from intent | Guided `specify`, `plan`, and `tasks` workflows |\n| Keep agents aligned | Repository-native mission artifacts under `kitty-specs/` |\n| Split implementation | Work packages with lifecycle lanes such as `planned`, `in_progress`, `for_review`, `approved`, and `done` |\n| Avoid branch chaos | Isolated git worktrees under `.worktrees/` |\n| See progress | Optional local kanban dashboard with `spec-kitty dashboard` |\n| Integrate agents | Slash commands or skills for common AI coding tools |\n| Learn from missions | Every completed mission generates a retrospective by default. Tune via `.kittify/config.yaml#retrospective` or charter; see [how-to](docs/how-to/use-retrospective-learning.md). |\n\n## Quick Start\n\nInstall the CLI:\n\n```bash\npipx install spec-kitty-cli\n```\n\n`pipx` is the preferred installer for the CLI because it keeps Spec Kitty in its\nown virtual environment and avoids the `externally-managed-environment` errors\ncommon on modern Linux distributions.\n\nOther supported install methods:\n\n```bash\nuv tool install spec-kitty-cli\n# or, inside an activated virtual environment\npython -m pip install spec-kitty-cli\n```\n\nCreate or initialize a project:\n\n```bash\nspec-kitty init my-project --ai claude\ncd my-project\nspec-kitty verify-setup\n```\n\nReplace `claude` with your agent key when needed. Common choices include `codex`, `cursor`, `gemini`, `copilot`, `opencode`, `qwen`, `windsurf`, `kiro`, `vibe`, `pi`, and `letta`.\n\nOpen your AI coding agent in the project and run the core workflow:\n\n```text\n/spec-kitty.charter\n/spec-kitty.specify Build a small task list app.\n/spec-kitty.plan\n/spec-kitty.tasks\n```\n\nThen let the runtime choose the next action until the mission is ready:\n\n```bash\nspec-kitty next --agent claude --mission \u003cmission-slug\u003e\n```\n\nReview, accept, merge, and close the loop:\n\n```text\n/spec-kitty.review\n/spec-kitty.accept\n/spec-kitty.merge --push\n```\n\nAfter merge, run `/spec-kitty-mission-review`. The mission's\n`retrospective.yaml` is authored during the runtime terminus (HiC prompt or\nautonomous facilitator), not by `merge`. Once it exists, use\n`spec-kitty retrospect summary` for the cross-mission view and\n`spec-kitty agent retrospect synthesize --mission \u003cmission-slug\u003e` to apply any\nstaged proposals (dry-run by default — pass `--apply` to mutate).\n\nFor the full walkthrough, see [Your First Feature](docs/tutorials/your-first-feature.md).\n\n## Everyday Commands\n\n| Command | Purpose |\n| --- | --- |\n| `spec-kitty init . --ai \u003cagent\u003e` | Add Spec Kitty to the current repo |\n| `spec-kitty verify-setup` | Check local installation and project wiring |\n| `spec-kitty dashboard` | Open the local mission dashboard |\n| `spec-kitty next --agent \u003cagent\u003e --mission \u003cslug\u003e` | Ask Spec Kitty what the agent should do next |\n| `spec-kitty upgrade` | Update an existing project after upgrading the CLI |\n| `spec-kitty --help` | Show available commands |\n\n## Documentation\n\nStart here:\n\n- [Getting Started](docs/tutorials/getting-started.md)\n- [Your First Feature](docs/tutorials/your-first-feature.md)\n- [CLI Command Reference](docs/reference/cli-commands.md)\n- [Slash Commands](docs/reference/slash-commands.md)\n- [Supported Agents](docs/reference/supported-agents.md)\n- [Dashboard Guide](docs/how-to/use-dashboard.md)\n- [Install and Upgrade](docs/how-to/install-and-upgrade.md)\n\nDeeper topics:\n\n- [Spec-Driven Development](docs/explanation/spec-driven-development.md)\n- [Mission System](docs/explanation/mission-system.md)\n- [Git Worktrees](docs/explanation/git-worktrees.md)\n- [Multi-Agent Orchestration](docs/explanation/multi-agent-orchestration.md)\n- [External Orchestrator Runbook](docs/how-to/run-external-orchestrator.md)\n- [Hosted Sync Workspaces](docs/how-to/sync-workspaces.md)\n\nHosted auth, sync, and tracker flows remain opt-in today. Internal /\npre-launch operators dogfooding the hidden hosted-readiness mode behind\n`SPEC_KITTY_ENABLE_SAAS_SYNC=1` should read\n[Internal Hosted-Readiness (Pre-Launch)](docs/how-to/internal-hosted-readiness.md).\nThe launch-day behavior that will replace today's defaults is staged\nunder [Launch-Readiness Behavior (Coming Soon)](docs/explanation/launch-readiness-future.md).\n\n## Development\n\n```bash\ngit clone https://github.com/Priivacy-ai/spec-kitty.git\ncd spec-kitty\npip install -e \".[test]\"\n```\n\nWhen testing templates from a source checkout:\n\n```bash\nexport SPEC_KITTY_TEMPLATE_ROOT=\"$(pwd)\"\nspec-kitty init my-project --ai claude\n```\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md) for contribution guidelines.\n\n## Identity-Boundary CI Gate\n\nThe `drift-detector` required check runs\n`tests/sync/test_diagnose.py::TestCanonicalRegistryRecognition` on every PR\nagainst `main`. It catches drift between the canonical registries in this\nrepo and the consumer-recognition contract that\n`spec-kitty-end-to-end-testing#41` closed over an 8-RC peeling cycle\n(rc14 → rc22). Workflow file:\n[`.github/workflows/drift-detector.yml`](.github/workflows/drift-detector.yml).\n\nThis is one of three coordinated CI gates tracked under\n[`#1247`](https://github.com/Priivacy-ai/spec-kitty/issues/1247):\n\n- `drift-detector` here (this repo).\n- `cross-repo-harness-tests` in [`spec-kitty-events`](https://github.com/Priivacy-ai/spec-kitty-events) — workflow `.github/workflows/cross-repo-harness-tests.yml`.\n- `identity-boundary-canary` in [`spec-kitty-saas`](https://github.com/Priivacy-ai/spec-kitty-saas) — workflow `.github/workflows/canary-gate.yml`.\n\nThis repo's drift-detector pins no external SHA — it only runs an in-repo\ntest. The sibling repos' workflows pin a specific commit of\n`Priivacy-ai/spec-kitty-end-to-end-testing`; see each sibling's README\n\"Identity-Boundary CI Gate\" section for the SHA-bump procedure.\n\n**Admin action required (one-time per repo)**: after this gate merges, a\nrepo admin must register the check as required on `main`:\n\n1. Open https://github.com/Priivacy-ai/spec-kitty/settings/branches.\n2. Edit the rule for `main`.\n3. Under \"Require status checks to pass before merging\", add the exact\n   name `drift-detector`.\n4. Save.\n\nUntil that step is done, the workflow still runs on every PR but its\nred status does not block merge.\n\n## Support\n\n- Open a [GitHub issue](https://github.com/Priivacy-ai/spec-kitty/issues/new) for bugs, feature requests, or questions.\n- See [CHANGELOG.md](CHANGELOG.md) for release notes.\n- See [CONTRIBUTORS.md](CONTRIBUTORS.md) and the [GitHub contributors graph](https://github.com/Priivacy-ai/spec-kitty/graphs/contributors) for contributor credits.\n\n## License\n\nSpec Kitty is released under the [MIT License](LICENSE).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fpriivacy-ai%2Fspec-kitty","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fpriivacy-ai%2Fspec-kitty","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fpriivacy-ai%2Fspec-kitty/lists"}