Does spec-kitty auto-invoke its skills?

Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.

Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.

Development

Plugin

spec-kitty

Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.

FLOW.md

priivacy-ai@priivacy-ai

GitHub

Plugin Signal90/100Strong

maintained100

capable84

documented100

adopted68

Install

$ npx -y skills add Priivacy-ai/spec-kitty --agent claude-code

Run the curl in your terminal, the rest in Claude Code.

Stats

Python Bash Linux Git GitHub

+2 tags

Anthropic Gemini

1,491

Stars

137

Forks

Active

Maintenance

Python

Language

MIT

License

3h ago

Last commit

10mo ago

Created

Repo: Priivacy-ai/spec-kitty

In this plugin

53 skills 1 command

See everything inside

What's inside

Skills

/ad-hoc-profile-loadLegacy alias for resolver-backed profile loading. Use the canonical spk-doctrine-profile-load skill for identity, boundaries, and governance. Triggers: "act as the architect", "load the reviewer profile", "switch to researcher", "use the planner role", "adopt a profile"./adversarial-squadDeploy a bounded, profile-loaded adversarial review squad at an SDD point-cut (post-spec, post-plan, post-tasks, pre-merge, or an ad-hoc decision) so independent doctrine lenses converge on findings one reviewer would miss. Triggers: "deploy a squad", "adversarial squad",/spec-kitty-bulk-edit-classificationRecognize when a mission is a bulk edit and drive the occurrence-classification guardrail on the user's behalf. Triggers: user says any variant of "rename X to Y", "change the terminology", "migrate all occurrences", "replace across the codebase", "the X feature is now the Y /spec-kitty-charter-doctrineRun charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers:/spec-kitty-git-workflowUnderstand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management",/spec-kitty-glossary-contextCurate and apply canonical terminology across Spec Kitty missions. Triggers: "update the glossary", "use canonical terms", "check terminology", "add a term", "fix term drift", "glossary conflicts", "resolve ambiguity", "review terminology consistency". Does NOT handle: runtime

Show all 53 skills

/spec-kitty-implement-reviewOrchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review /spec-kitty-mission-reviewReview a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission /spec-kitty-mission-systemUnderstand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 5-tier chain, and how doctrine artifacts (procedures, tactics,/spec-kitty-orchestrator-api-operatorTeach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI. Triggers: "use orchestrator-api", "build a custom orchestrator", "automate externally", "integrate CI with spec-kitty", "call spec-kitty from another tool",/spec-kitty-program-orchestrateOrchestrate a multi-repo, multi-mission Spec Kitty program end-to-end: run specify → plan → tasks → implement → review → merge → mission-review → post-merge fixes across several repositories in a defined dependency order, using background sub-agents for parallel work and a /spec-kitty-runtime-nextDrive the canonical spec-kitty next --mission <handle> control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should /spec-kitty-runtime-reviewReview runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this /spec-kitty-setup-doctorInstall, verify, and recover the modern Spec Kitty 2.0.11+ operating surface. Triggers: "set up Spec Kitty", "skills missing", "next is blocked", "runtime is broken", "doctrine assets are missing", "my agent can't find the skills". Does NOT handle: generic coding questions with /spec-kitty-spdd-reasonsDrive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this /spec-kittyStandalone Spec Kitty governance invocation: run Spec Kitty when the user indicates they want Spec Kitty involved, load governance context, open an Op, do the work under that context, and close the Op with the real outcome. Documents dispatch, profiles list, invocations list,/spk-admin-agent-configConfigure Spec Kitty agent profiles, host-specific paths, command installation, and model/tool routing./spk-admin-dashboardOpen or report the Spec Kitty dashboard. Use for dashboard URL, localhost daemon metadata in .kittify/.dashboard, --open, --kill, or status views./spk-admin-git-workflowOperate Spec Kitty git workflows, worktrees, safe commits, merge preflights, stale state checks, and recovery./spk-admin-setup-doctorInstall, verify, and repair Spec Kitty commands, skills, agent paths, runtime prerequisites, and common setup failures./spk-admin-upgradeUpgrade Spec Kitty installations and repair generated commands, skills, migrations, and compatibility shims./spk-doctrine-bulk-editRecognize bulk-edit missions and apply occurrence classification guardrails before modifying many matching instances./spk-doctrine-charterRun Spec Kitty charter interview, generation, context loading, and synchronization workflows./spk-doctrine-glossaryCurate and apply Spec Kitty glossary terminology, canonical terms, aliases, conflicts, and semantic drift checks./spk-doctrine-profile-loadLoad a Spec Kitty agent profile on demand for interactive sessions, including identity, governance scope, boundaries, and initialization./spk-doctrine-semantic-compressionInvoke Randy Reducer and semantic-compression doctrine for behavior-preserving code reduction./spk-doctrine-spdd-reasonsDrive REASONS Canvas authoring and review for missions using Spec Kitty Structured-Prompt-Driven Development./spk-gate-acceptRun the Spec Kitty accept gate for a completed mission and verify final readiness before merge./spk-gate-mergeMerge an accepted Spec Kitty mission safely, preserving git invariants, mission state, and post-merge follow-through./spk-gate-mission-reviewRun post-merge Spec Kitty mission review for spec-to-code fidelity, FR coverage, drift, risk, and final verdict./spk-gate-retrospectiveCreate or verify Spec Kitty mission retrospectives after merge and surface process learnings without blocking completed work./spk-integrate-orchestrator-apiUse Spec Kitty orchestrator-api from external systems, respecting host boundaries, state contracts, and workflow commands./spk-meta-skill-authoringAuthor future Spec Kitty spk skills using the 3.2.0 naming convention, lifecycle families, and doctrine/command boundaries./spk-meta-skill-mapDiscover the Spec Kitty 3.2.0 spk skill hierarchy, naming convention, legacy aliases, and the correct skill for a user intent./spk-mission-documentationOperate documentation-oriented Spec Kitty missions and ensure docs stay tied to shipped behavior and doctrine./spk-mission-planOperate the Spec Kitty plan phase: convert a completed spec into architecture, data flow, risks, and implementation strategy./spk-mission-researchOperate pre-spec or in-mission research workflows while keeping findings tied to mission decisions./spk-mission-specifyOperate the Spec Kitty specify phase: turn user intent into a mission spec while preserving scope, ambiguity, and acceptance criteria./spk-mission-tasksOperate Spec Kitty task and work-package authoring, including tasks outline, package slicing, and finalization./spk-mission-typesExplain Spec Kitty mission types, step contracts, action indices, and when to choose each mission workflow./spk-run-blocked-recoveryRecover from Spec Kitty blocked runtime states, missing artifacts, failed guards, stale worktrees, and decision-required loops./spk-run-implement-reviewOrchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected./spk-run-nextDrive the canonical spec-kitty next control loop and route query, step, blocked, decision_required, and terminal results./spk-run-program-orchestrateOrchestrate multi-repo, multi-mission Spec Kitty programs across dependencies, parallel agents, review gates, merge, and post-merge closeout./spk-run-review-wpReview a Spec Kitty work package through the runtime review surface and approve or reject with structured feedback./spk-start-agent-surfaceChoose the correct Spec Kitty workflow for Codex CLI, Claude Code, and supported slash-command or command-skill harnesses./spk-start-command-mapMap Spec Kitty slash commands and CLI entry points to spk skills. Use when choosing /spec-kitty.* commands or explaining command-skill boundaries./spk-start-first-featureGuide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective./spk-start-hereStart here for Spec Kitty. Orient CLI users and supported agent-harness users; choose the right command, skill family, and recovery path./spk-team-authHandle Spec Kitty team authentication, hosted credentials, account selection, and auth-related recovery./spk-team-connectorsOperate Spec Kitty connector integrations and route connector work across tracker, sync, SaaS, and external services./spk-team-syncOperate Spec Kitty team sync, hosted SaaS sync, offline queue, diagnostics, and recovery flows./spk-team-trackerOperate Spec Kitty tracker workflows, tracker service discovery, binding, hosted routing, and tracker recovery.

Commands

/ERROR_CODES**Source of truth**: `src/specify_cli/cli/commands/review/_diagnostics.py` (StrEnum class `MissionReviewDiagnostic`). This file is a hand-maintained mirror. Until #645's code-to-docs flow exists, the StrEnum members and this file's section count must match per NFR-008.

Badges

README

Read on GitHub

Spec Kitty is an open-source CLI for turning product intent into a repo-native AI coding workflow:

spec -> plan -> tasks -> next -> review -> accept -> merge

Use it to build a governed software factory around Claude Code, Codex, Cursor, Gemini, GitHub Copilot, Windsurf, OpenCode, and other AI coding agents. Spec Kitty keeps specs, plans, work packages, acceptance criteria, review state, and merge decisions in your repository, then gives agents isolated git worktrees so implementation can happen in parallel without branch chaos.

Bright Software Factory, Not a Black Box

Spec Kitty is for teams building software factories: repeatable inputs, clear work-package boundaries, isolated execution, visible progress, and review gates. It can support dark software factories and autonomous coding experiments, but it is deliberately not a lights-out black box by default. Humans define intent, architecture, and acceptance criteria; agents implement inside traceable worktrees; reviewers accept, reject, or merge with an audit trail.

The goal is not more prompt text. The goal is a durable operating system for agentic coding where the repository remains the source of truth.

Is It For You?

Use Spec Kitty when:

AI coding sessions are losing requirements, decisions, or acceptance criteria.
You want specs, plans, tasks, reviews, and merge state stored in Git.
Multiple agents or developers need clear work-package boundaries.
You are running parallel Claude Code, Codex, Cursor, Copilot, Gemini, or Windsurf work and need git worktree isolation.
You are moving from vibe coding to a repeatable spec-driven development workflow.
You want a local workflow first, with optional hosted tracker and sync integrations later.

It is probably overkill for one-off edits, tiny scripts, or teams that do not use Git.

What It Provides

Need	Spec Kitty provides
Start from intent	Guided `specify`, `plan`, and `tasks` workflows
Keep agents aligned	Repository-native mission artifacts under `kitty-specs/`
Split implementation	Work packages with lifecycle lanes such as `planned`, `in_progress`, `for_review`, `approved`, and `done`
Run agents in parallel	Isolated git worktrees under `.worktrees/`
Keep quality visible	Review, accept, merge, and retrospective gates
See progress	Optional local kanban dashboard with `spec-kitty dashboard`
Integrate agents	Slash commands or skills for Claude Code, Codex, Cursor, Gemini, Copilot, Windsurf, OpenCode, and more
Learn from missions	Every completed mission generates a retrospective by default. Tune via `.kittify/config.yaml#retrospective` or charter; see how-to.

Common Use Cases

Replace ad hoc vibe coding with spec-driven development.
Turn GitHub issues, product requirements, or bug reports into executable work packages.
Coordinate multiple AI coding agents without losing context between sessions.
Keep architecture decisions, constraints, and acceptance criteria close to the code.
Build a governed software factory that can scale toward more autonomy without hiding review, test, or merge decisions.

Governance layer

Spec Kitty keeps runtime governance in the repo instead of treating it as agent-only prompt text. The trail model in docs/trail-model.md describes how spec-kitty dispatch "<request>" maps operator intent to runtime behavior, while docs/host-surface-parity.md tracks parity across CLI, slash-command, and hosted surfaces.

The primary standalone governance command is:

spec-kitty dispatch "<request>" - loads governance context, opens an Op record, and returns the context the agent must use before doing the work

Quick Start

Install the CLI:

pipx install spec-kitty-cli

pipx is the preferred installer for the CLI because it keeps Spec Kitty in its own virtual environment and avoids the externally-managed-environment errors common on modern Linux distributions.

Other supported install methods:

uv tool install spec-kitty-cli
# or, inside an activated virtual environment
python -m pip install spec-kitty-cli

Create or initialize a project:

spec-kitty init my-project --ai claude
cd my-project
spec-kitty verify-setup

Replace claude with your agent key when needed. Common choices include codex, cursor, gemini, copilot, opencode, qwen, windsurf, kiro, vibe, pi, and letta. See Supported Agents for the current list.

Open your AI coding agent in the project and run the core workflow:

/spec-kitty.charter
/spec-kitty.specify Build a small task list app.
/spec-kitty.plan
/spec-kitty.tasks

Then let the runtime choose the next action until the mission is ready:

spec-kitty next --agent claude --mission <mission-slug>

Review, accept, merge, and close the loop:

/spec-kitty.review
/spec-kitty.accept
/spec-kitty.merge --push

After merge, run /spec-kitty-mission-review. The mission's retrospective.yaml is authored during the runtime terminus (HiC prompt or autonomous facilitator), not by merge. Once it exists, use spec-kitty retrospect summary for the cross-mission view and spec-kitty agent retrospect synthesize --mission <mission-slug> to apply any staged proposals (dry-run by default — pass --apply to mutate).

For the full walkthrough, see Your First Mission.

Everyday Commands

Command	Purpose
`spec-kitty init . --ai <agent>`	Add Spec Kitty to the current repo
`spec-kitty verify-setup`	Check local installation and project wiring
`spec-kitty dashboard`	Open the local mission dashboard
`spec-kitty next --agent <agent> --mission <slug>`	Ask Spec Kitty what the agent should do next
`spec-kitty upgrade`	Update an existing project after upgrading the CLI
`spec-kitty --help`	Show available commands

Documentation

Start here:

Deeper topics:

Hosted auth, sync, and tracker flows remain opt-in. For setup details, see Hosted Sync Workspaces, Internal Hosted-Readiness, and Launch-Readiness Behavior.

FAQ

Is Spec Kitty for dark software factories?

Spec Kitty can be used as part of a dark software factory or autonomous coding pipeline, but its default model is governed and human-in-loop. It keeps specs, work packages, agent actions, review decisions, and merge state visible in the repository.

Which AI coding agents does Spec Kitty support?

Spec Kitty supports common AI coding agents and coding harnesses including Claude Code, Codex, Cursor, Gemini, GitHub Copilot, OpenCode, Qwen, Windsurf, Kiro, Vibe, Pi, and Letta. See Supported Agents.

How is Spec Kitty different from prompt templates or Spec Kit?

Spec Kitty is inspired by spec-driven development workflows, but adds repo-native mission state, work-package lanes, git worktree isolation, a local dashboard, governance commands, and an explicit next -> review -> accept -> merge runtime loop.

Does Spec Kitty require a SaaS service?

No. Spec Kitty is local-first and stores its core artifacts in your repo. Hosted tracker and sync integrations are optional.

Development

git clone https://github.com/Priivacy-ai/spec-kitty.git
cd spec-kitty
pip install -e ".[test]"

When testing templates from a source checkout:

export SPEC_KITTY_TEMPLATE_ROOT="$(pwd)"
spec-kitty init my-project --ai claude

See the Contributing guide for contribution guidelines.

Identity-Boundary CI Gate

The drift-detector required check protects the shared identity-boundary contract across Spec Kitty repos. Contributor and admin details live in Identity-Boundary CI Gate.

Support

Open a GitHub issue for bugs, feature requests, or questions.
See the changelog for release notes.
See CONTRIBUTORS.md and the GitHub contributors graph for contributor credits.

License

Spec Kitty is released under the MIT License.

File tree

1680

Priivacy-ai/spec-kittyView on GitHub

.agent/
  workflows/
    spec-kitty-standalone.md
.all-contributorsrc
.amazonq/
  prompts/
    spec-kitty-standalone.md
.augment/
  commands/
    spec-kitty-standalone.md
.claudeignore
.cursor/
  commands/
    spec-kitty-standalone.md
.gemini/
  commands/
    spec-kitty-standalone.md
.gitattributes
.github/
  CHANGELOG.md
  CODEOWNERS
  CONTRIBUTING.md
  ISSUE_TEMPLATE/
    bug_report.md
    config.yml
    enhancement_request.md
    idea_brainstorm.md
  prompts/
    spec-kitty-standalone.md
  PULL_REQUEST_TEMPLATE.md
  workflows/
    all-contributors-normalize.yml
    all-contributors-sync.yml
    canonical-producer-lint.yml
    check-spec-kitty-events-alignment.yml
    ci-quality.yml
    ci-windows.yml
    docs-freshness.yml
    docs-pages.yml
    doctrine-charter-tests.yml
    drift-detector.yml
    mutation-remediation.md
    orchestrator-boundary.yml
    plugin-validate.yml
    protect-main.yml
    release-readiness.yml
    release.yml
    scripts/
      check-release-exists.sh
      create-github-release.sh
      create-release-packages.sh
      generate-release-notes.sh
      get-next-version.sh
      update-version.sh
    teamspace-mission-state-readiness.yml
    ui-e2e.yml
.gitignore
.kilocode/
  workflows/
    spec-kitty-standalone.md
.kiro/
  prompts/
    spec-kitty-standalone.md
.kittify/
  agent_profiles_manifest.json
  charter/
    charter.md
    charter.yaml
    directives.yaml
    governance.yaml
    graph.yml
    interview/
      answers.yaml
    metadata.yaml
    references.yaml
    synthesis-manifest.yaml
  command-skills-manifest.json
  config.yaml
  curation/
    state.json
  doctrine/
    directive/
      .provenance/
        DIRECTIVE_evidence_logs_must_persist.yaml
        DIRECTIVE_terminus_retrospective_always_on.yaml
      DIRECTIVE_evidence_logs_must_persist.md
      DIRECTIVE_terminus_retrospective_always_on.md
    overlays/
      calibration-documentation.yaml
      calibration-erp-custom.yaml
      calibration-research.yaml
      calibration-software-dev.yaml
    procedure/
      .provenance/
        PROCEDURE_cross_namespace_owned_files_autodetect.yaml
        PROCEDURE_issue_matrix_autoscaffold.yaml
      PROCEDURE_cross_namespace_owned_files_autodetect.md
      PROCEDURE_issue_matrix_autoscaffold.md
    tactic/
      .provenance/
        TACTIC_mirror_external_issue_numbering.yaml
      TACTIC_mirror_external_issue_numbering.md
  evidence/
    01KTTCEAF0WTVAHYGND1D16R68/
      evidence.md
      record.json
    01KTTDPPRCKWC85S4AB848FYD7/
      evidence.md
      record.json
    01KTTDPRW03BT53YT5XBWPVNZB/
      evidence.md
      record.json
    01KTTDT7BJB6FCVS71BX5V4429/
      evidence.md
      record.json
    01KTTMYQQFANE2X67MWEXFYVC6/
      evidence.md
      record.json
    01KTY6AN6Y74EG53ECHE7AN0Y7/
      evidence.md
      record.json
    01KTY78CYHFRK9GPCB956MCNCX/
      evidence.md
      record.json
    01KTY78F3DCC7WEFRYYAVS3FQ8/
      evidence.md
      record.json
    01KTY78H7CDFEPB4TPKYNAE44T/
      evidence.md
      record.json
    01KTYDGYWA595WBFCH8WSYHVNT/
      evidence.md
      record.json
    01KTYE0C9CF75FQN8127JP33B3/
      evidence.md
      record.json
    01KTYE0EDV12HCQZB2BFPXNBZ2/
      evidence.md
      record.json
    01KTYW56FW34KY6FM6J0C90GHT/
      evidence.md
      record.json
    01KTYW5NC527B19TCY05M6ZE5D/
      evidence.md
      record.json
    01KTYX4A095KW707C2EBJQPPBN/
      evidence.md
      record.json
    01KTYXF27M5X8AG57BBN1QDJZ5/
      evidence.md
      record.json
    01KTYXNMGTJXSP9B7R3YKP07S2/
      evidence.md
      record.json
    01KTYY3HDT1D1N4SB2XFJNHDFJ/
      evidence.md
      record.json
    01KTYYFC60ZGDEAE4VWWP96YV5/
      evidence.md
      record.json
    01KTZXE73F2WT2X3WNNW3Q4PVJ/
      evidence.md
      record.json
    01KTZYFM79XGAPFSNPT3JZGA52/
      evidence.md
      record.json
    01KTZYGBS72367S0YCHBWDHE5G/
      evidence.md
      record.json
    01KTZYJGPHSQRBE29Q6HBNQPP8/
      evidence.md
      record.json
    01KTZZJAHP3MYRDXRW6PM5CZQQ/
      evidence.md
      record.json
    01KV00KSKPYNTHT9V1CAZ0QS6A/
      evidence.md
      record.json
    01KV00MNXGAHVV90778DKKS5K0/
      evidence.md
      record.json
    01KV00SRGSVTWSF3TV2G7M0BPX/
      evidence.md
      record.json
    01KV0421T7MFHS014E6P8348EA/
      evidence.md
      record.json
    01KV07VEY31YEQTCR22JQ3GHEM/
      evidence.md
      record.json
    01KV091MHWGN2YR0PT0NVB3W04/
      evidence.md
      record.json
    01KV0927XG6B59261E04SJTBYN/
      evidence.md
      record.json
    01KV0AQX3T85C1A8GVAVCVEMTJ/
      evidence.md
      record.json
    01KV0AY91FDE1DK671QN1N5K9G/
      evidence.md
      record.json
    01KV0B4AMNGG8P8FN4CZ6RST4M/
      evidence.md
      record.json
    01KV0CQZCG0Z9AT6ZZVSB0STQ7/
      evidence.md
      record.json
    01KV0DTPSAQ9QA3ATXRV2RNGT8/
      evidence.md
      record.json
    01KV0EQZTF5R063KY5EN5FPK44/
      evidence.md
      record.json
    01KV0F0DZYFDWYVSJFCEP2FZQ1/
      evidence.md
      record.json
    01KV0T72ETKNZ990ZKCNZ947W7/
      evidence.md
      record.json
    01KV62CR3XY4ASSRP4WA2BB80A/
      evidence.md
      record.json
    01KV6KJNJTJ0KJWKSHE9NHN0H1/
      evidence.md
      record.json
    01KV6KYEPR7HKMZ3TPEV6W2JPF/
      evidence.md
      record.json
    01KV6M00VRPFZNZEPJ46YR76B8/
      evidence.md
      record.json
    01KV6M4ZFSTE4YNN1JX6BSH6NX/
      evidence.md
      record.json
    01KXAC5G04RVH5P9CDJ8MKKG69/
      evidence.md
      record.json
    01KY0QAADWA0YXA3VGKXV1WVWA/
      evidence.md
      record.json
    01KZ5PRAH2YN2CTYM18TPT0T4Y/
      evidence.md
      record.json
    01KZ5RFY5WHPPQ02KPZB39274J/
      evidence.md
      record.json
  glossaries/
    planning-and-tracking.yaml
    spec_kitty_core.yaml
  legacy-warning-shown-01KTNWFC3B1ZGFR9FTT77X7H2Y
  memory/
    058-architectural-review.md
    available_tooling.md
    README.md
    templates/
      POWERSHELL_SYNTAX.md
  metadata.yaml
  migrations/
    mission-state/
      109dbcfa005326f4.json
      22a5a9d3195f1833.json
      73d2ecec75f25774.json
      9f083618f5db308b.json
      cf4abc4ad816579a.json
      e35c2e74babb3f04.json
      quarantine/
        109dbcfa005326f4/
          charter-end-user-docs-828-01KQCSYD/
            status.events.jsonl
          cli-session-survival-daemon-singleton-01KQ9M3M/
            status.events.jsonl
          private-teamspace-ingress-safeguards-01KQH03Y/
            status.events.jsonl
          stable-320-release-blocker-cleanup-01KQW4DF/
            status.events.jsonl
        c680177cc61d4709/
          charter-deadcode-noop-campsite-01KXW0NY/
            status.events.jsonl
          ci-topology-shrink-01KWQAVX/
            status.events.jsonl
          codebase-sanitization-1060-1622-01KV5F0B/
            status.events.jsonl
          docs-ia-onboarding-overhaul-01KY02JB/
            status.events.jsonl
          doctrine-silence-guards-01KYFV7Q/
            status.events.jsonl
          doctrine-tension-edges-01KY1WPC/
            status.events.jsonl
          mission-type-doctrine-authority-01KXH6GE/
            status.events.jsonl
          read-path-error-fidelity-adoption-01KV8NPC/
            status.events.jsonl
          write-side-context-factory-adoption-01KV9W0X/
            status.events.jsonl
  missions/
    01KT6HVH3QND4Q3KCGH2419N4J/
      retrospective.yaml
    01KTDVHZKGCHCW6HQ4V577PNES/
      retrospective.yaml
    01KTSJ2H8E5YF2EGJYGAE5Z5Q2/
      retrospective.yaml
  overrides/
    AGENTS.md
    missions/
      __init__.py
      action_index.py
      documentation/
        command-templates/
          implement.md
          plan.md
          README.md
          review.md
          specify.md
          tasks.md
        expected-artifacts.yaml
        mission.yaml
        README.md
        templates/
          divio/
            explanation-template.md
            howto-template.md
            README.md
            reference-template.md
            tutorial-template.md
          generators/
            jsdoc.json.template
            README.md
            sphinx-conf.py.template
          plan-template.md
          README.md
          release-template.md
          spec-template.md
          task-prompt-template.md
          tasks-template.md
      glossary_hook.py
      models.py
      plan/
        command-templates/
          plan.md
          README.md
          research.md
          review.md
          specify.md
        mission-runtime.yaml
        mission.yaml
        README.md
        templates/
          .gitkeep
          README.md
      primitives.py
      README.md
      repository.py
      research/
        command-templates/
          implement.md
          plan.md
          README.md
          review.md
          specify.md
          tasks.md
        expected-artifacts.yaml
        mission.yaml
        README.md
        templates/
          data-model-template.md
          plan-template.md
          README.md
          research/
          research-template.md
            evidence-log.csv
            README.md
            source-register.csv
          spec-template.md
          task-prompt-template.md
          tasks-template.md
      software-dev/
        actions/
          implement/
            guidelines.md
            index.yaml
          plan/
            guidelines.md
            index.yaml
          review/
            guidelines.md
            index.yaml
          specify/
            guidelines.md
            index.yaml
        command-templates/
          accept.md
          analyze.md
          constitution.md
          dashboard.md
          implement.md
          plan.md
          README.md
          review.md
          specify.md
... 1600 more

Showing a partial view of a very large repo.

FAQ

spec-kitty is a Claude Code plugin with 53 hand-picked skills for development work, indexed on Flowy. Install it with the command on its page. It includes ad-hoc-profile-load, adversarial-squad, spec-kitty-bulk-edit-classification. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.

What is spec-kitty?: Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
How do I install spec-kitty?: Run these in Claude Code: npx -y skills add Priivacy-ai/spec-kitty --agent claude-code. Then prompt normally.
Does spec-kitty auto-invoke its skills?: Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
Is spec-kitty free?: Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.

Development

Plugin

spec-kitty

Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.

FLOW.md

priivacy-ai@priivacy-ai

GitHub

Plugin Signal90/100Strong

maintained100

capable84

documented100

adopted68

Install

$ npx -y skills add Priivacy-ai/spec-kitty --agent claude-code

Run the curl in your terminal, the rest in Claude Code.

Stats

Python Bash Linux Git GitHub

+2 tags

Anthropic Gemini

1,491

Stars

137

Forks

Active

Maintenance

Python

Language

MIT

License

3h ago

Last commit

10mo ago

Created

Repo: Priivacy-ai/spec-kitty

In this plugin

53 skills 1 command

See everything inside

What's inside

Skills

Show all 53 skills

Commands

Badges

README

Read on GitHub

Spec Kitty is an open-source CLI for turning product intent into a repo-native AI coding workflow:

spec -> plan -> tasks -> next -> review -> accept -> merge

Bright Software Factory, Not a Black Box

The goal is not more prompt text. The goal is a durable operating system for agentic coding where the repository remains the source of truth.

Is It For You?

Use Spec Kitty when:

AI coding sessions are losing requirements, decisions, or acceptance criteria.
You want specs, plans, tasks, reviews, and merge state stored in Git.
Multiple agents or developers need clear work-package boundaries.
You are running parallel Claude Code, Codex, Cursor, Copilot, Gemini, or Windsurf work and need git worktree isolation.
You are moving from vibe coding to a repeatable spec-driven development workflow.
You want a local workflow first, with optional hosted tracker and sync integrations later.

It is probably overkill for one-off edits, tiny scripts, or teams that do not use Git.

What It Provides

Need	Spec Kitty provides
Start from intent	Guided `specify`, `plan`, and `tasks` workflows
Keep agents aligned	Repository-native mission artifacts under `kitty-specs/`
Split implementation	Work packages with lifecycle lanes such as `planned`, `in_progress`, `for_review`, `approved`, and `done`
Run agents in parallel	Isolated git worktrees under `.worktrees/`
Keep quality visible	Review, accept, merge, and retrospective gates
See progress	Optional local kanban dashboard with `spec-kitty dashboard`
Integrate agents	Slash commands or skills for Claude Code, Codex, Cursor, Gemini, Copilot, Windsurf, OpenCode, and more
Learn from missions	Every completed mission generates a retrospective by default. Tune via `.kittify/config.yaml#retrospective` or charter; see how-to.

Common Use Cases

Replace ad hoc vibe coding with spec-driven development.
Turn GitHub issues, product requirements, or bug reports into executable work packages.
Coordinate multiple AI coding agents without losing context between sessions.
Keep architecture decisions, constraints, and acceptance criteria close to the code.
Build a governed software factory that can scale toward more autonomy without hiding review, test, or merge decisions.

Governance layer

The primary standalone governance command is:

spec-kitty dispatch "<request>" - loads governance context, opens an Op record, and returns the context the agent must use before doing the work

Quick Start

Install the CLI:

pipx install spec-kitty-cli

pipx is the preferred installer for the CLI because it keeps Spec Kitty in its own virtual environment and avoids the externally-managed-environment errors common on modern Linux distributions.

Other supported install methods:

uv tool install spec-kitty-cli
# or, inside an activated virtual environment
python -m pip install spec-kitty-cli

Create or initialize a project:

spec-kitty init my-project --ai claude
cd my-project
spec-kitty verify-setup

Open your AI coding agent in the project and run the core workflow:

/spec-kitty.charter
/spec-kitty.specify Build a small task list app.
/spec-kitty.plan
/spec-kitty.tasks

Then let the runtime choose the next action until the mission is ready:

spec-kitty next --agent claude --mission <mission-slug>

Review, accept, merge, and close the loop:

/spec-kitty.review
/spec-kitty.accept
/spec-kitty.merge --push

For the full walkthrough, see Your First Mission.

Everyday Commands

Command	Purpose
`spec-kitty init . --ai <agent>`	Add Spec Kitty to the current repo
`spec-kitty verify-setup`	Check local installation and project wiring
`spec-kitty dashboard`	Open the local mission dashboard
`spec-kitty next --agent <agent> --mission <slug>`	Ask Spec Kitty what the agent should do next
`spec-kitty upgrade`	Update an existing project after upgrading the CLI
`spec-kitty --help`	Show available commands

Documentation

Start here:

Deeper topics:

Hosted auth, sync, and tracker flows remain opt-in. For setup details, see Hosted Sync Workspaces, Internal Hosted-Readiness, and Launch-Readiness Behavior.

FAQ

Is Spec Kitty for dark software factories?

Which AI coding agents does Spec Kitty support?

How is Spec Kitty different from prompt templates or Spec Kit?

Does Spec Kitty require a SaaS service?

No. Spec Kitty is local-first and stores its core artifacts in your repo. Hosted tracker and sync integrations are optional.

Development

git clone https://github.com/Priivacy-ai/spec-kitty.git
cd spec-kitty
pip install -e ".[test]"

When testing templates from a source checkout:

export SPEC_KITTY_TEMPLATE_ROOT="$(pwd)"
spec-kitty init my-project --ai claude

See the Contributing guide for contribution guidelines.

Identity-Boundary CI Gate

The drift-detector required check protects the shared identity-boundary contract across Spec Kitty repos. Contributor and admin details live in Identity-Boundary CI Gate.

Support

Open a GitHub issue for bugs, feature requests, or questions.
See the changelog for release notes.
See CONTRIBUTORS.md and the GitHub contributors graph for contributor credits.

License

Spec Kitty is released under the MIT License.

File tree

1680

Priivacy-ai/spec-kittyView on GitHub

.agent/
  workflows/
    spec-kitty-standalone.md
.all-contributorsrc
.amazonq/
  prompts/
    spec-kitty-standalone.md
.augment/
  commands/
    spec-kitty-standalone.md
.claudeignore
.cursor/
  commands/
    spec-kitty-standalone.md
.gemini/
  commands/
    spec-kitty-standalone.md
.gitattributes
.github/
  CHANGELOG.md
  CODEOWNERS
  CONTRIBUTING.md
  ISSUE_TEMPLATE/
    bug_report.md
    config.yml
    enhancement_request.md
    idea_brainstorm.md
  prompts/
    spec-kitty-standalone.md
  PULL_REQUEST_TEMPLATE.md
  workflows/
    all-contributors-normalize.yml
    all-contributors-sync.yml
    canonical-producer-lint.yml
    check-spec-kitty-events-alignment.yml
    ci-quality.yml
    ci-windows.yml
    docs-freshness.yml
    docs-pages.yml
    doctrine-charter-tests.yml
    drift-detector.yml
    mutation-remediation.md
    orchestrator-boundary.yml
    plugin-validate.yml
    protect-main.yml
    release-readiness.yml
    release.yml
    scripts/
      check-release-exists.sh
      create-github-release.sh
      create-release-packages.sh
      generate-release-notes.sh
      get-next-version.sh
      update-version.sh
    teamspace-mission-state-readiness.yml
    ui-e2e.yml
.gitignore
.kilocode/
  workflows/
    spec-kitty-standalone.md
.kiro/
  prompts/
    spec-kitty-standalone.md
.kittify/
  agent_profiles_manifest.json
  charter/
    charter.md
    charter.yaml
    directives.yaml
    governance.yaml
    graph.yml
    interview/
      answers.yaml
    metadata.yaml
    references.yaml
    synthesis-manifest.yaml
  command-skills-manifest.json
  config.yaml
  curation/
    state.json
  doctrine/
    directive/
      .provenance/
        DIRECTIVE_evidence_logs_must_persist.yaml
        DIRECTIVE_terminus_retrospective_always_on.yaml
      DIRECTIVE_evidence_logs_must_persist.md
      DIRECTIVE_terminus_retrospective_always_on.md
    overlays/
      calibration-documentation.yaml
      calibration-erp-custom.yaml
      calibration-research.yaml
      calibration-software-dev.yaml
    procedure/
      .provenance/
        PROCEDURE_cross_namespace_owned_files_autodetect.yaml
        PROCEDURE_issue_matrix_autoscaffold.yaml
      PROCEDURE_cross_namespace_owned_files_autodetect.md
      PROCEDURE_issue_matrix_autoscaffold.md
    tactic/
      .provenance/
        TACTIC_mirror_external_issue_numbering.yaml
      TACTIC_mirror_external_issue_numbering.md
  evidence/
    01KTTCEAF0WTVAHYGND1D16R68/
      evidence.md
      record.json
    01KTTDPPRCKWC85S4AB848FYD7/
      evidence.md
      record.json
    01KTTDPRW03BT53YT5XBWPVNZB/
      evidence.md
      record.json
    01KTTDT7BJB6FCVS71BX5V4429/
      evidence.md
      record.json
    01KTTMYQQFANE2X67MWEXFYVC6/
      evidence.md
      record.json
    01KTY6AN6Y74EG53ECHE7AN0Y7/
      evidence.md
      record.json
    01KTY78CYHFRK9GPCB956MCNCX/
      evidence.md
      record.json
    01KTY78F3DCC7WEFRYYAVS3FQ8/
      evidence.md
      record.json
    01KTY78H7CDFEPB4TPKYNAE44T/
      evidence.md
      record.json
    01KTYDGYWA595WBFCH8WSYHVNT/
      evidence.md
      record.json
    01KTYE0C9CF75FQN8127JP33B3/
      evidence.md
      record.json
    01KTYE0EDV12HCQZB2BFPXNBZ2/
      evidence.md
      record.json
    01KTYW56FW34KY6FM6J0C90GHT/
      evidence.md
      record.json
    01KTYW5NC527B19TCY05M6ZE5D/
      evidence.md
      record.json
    01KTYX4A095KW707C2EBJQPPBN/
      evidence.md
      record.json
    01KTYXF27M5X8AG57BBN1QDJZ5/
      evidence.md
      record.json
    01KTYXNMGTJXSP9B7R3YKP07S2/
      evidence.md
      record.json
    01KTYY3HDT1D1N4SB2XFJNHDFJ/
      evidence.md
      record.json
    01KTYYFC60ZGDEAE4VWWP96YV5/
      evidence.md
      record.json
    01KTZXE73F2WT2X3WNNW3Q4PVJ/
      evidence.md
      record.json
    01KTZYFM79XGAPFSNPT3JZGA52/
      evidence.md
      record.json
    01KTZYGBS72367S0YCHBWDHE5G/
      evidence.md
      record.json
    01KTZYJGPHSQRBE29Q6HBNQPP8/
      evidence.md
      record.json
    01KTZZJAHP3MYRDXRW6PM5CZQQ/
      evidence.md
      record.json
    01KV00KSKPYNTHT9V1CAZ0QS6A/
      evidence.md
      record.json
    01KV00MNXGAHVV90778DKKS5K0/
      evidence.md
      record.json
    01KV00SRGSVTWSF3TV2G7M0BPX/
      evidence.md
      record.json
    01KV0421T7MFHS014E6P8348EA/
      evidence.md
      record.json
    01KV07VEY31YEQTCR22JQ3GHEM/
      evidence.md
      record.json
    01KV091MHWGN2YR0PT0NVB3W04/
      evidence.md
      record.json
    01KV0927XG6B59261E04SJTBYN/
      evidence.md
      record.json
    01KV0AQX3T85C1A8GVAVCVEMTJ/
      evidence.md
      record.json
    01KV0AY91FDE1DK671QN1N5K9G/
      evidence.md
      record.json
    01KV0B4AMNGG8P8FN4CZ6RST4M/
      evidence.md
      record.json
    01KV0CQZCG0Z9AT6ZZVSB0STQ7/
      evidence.md
      record.json
    01KV0DTPSAQ9QA3ATXRV2RNGT8/
      evidence.md
      record.json
    01KV0EQZTF5R063KY5EN5FPK44/
      evidence.md
      record.json
    01KV0F0DZYFDWYVSJFCEP2FZQ1/
      evidence.md
      record.json
    01KV0T72ETKNZ990ZKCNZ947W7/
      evidence.md
      record.json
    01KV62CR3XY4ASSRP4WA2BB80A/
      evidence.md
      record.json
    01KV6KJNJTJ0KJWKSHE9NHN0H1/
      evidence.md
      record.json
    01KV6KYEPR7HKMZ3TPEV6W2JPF/
      evidence.md
      record.json
    01KV6M00VRPFZNZEPJ46YR76B8/
      evidence.md
      record.json
    01KV6M4ZFSTE4YNN1JX6BSH6NX/
      evidence.md
      record.json
    01KXAC5G04RVH5P9CDJ8MKKG69/
      evidence.md
      record.json
    01KY0QAADWA0YXA3VGKXV1WVWA/
      evidence.md
      record.json
    01KZ5PRAH2YN2CTYM18TPT0T4Y/
      evidence.md
      record.json
    01KZ5RFY5WHPPQ02KPZB39274J/
      evidence.md
      record.json
  glossaries/
    planning-and-tracking.yaml
    spec_kitty_core.yaml
  legacy-warning-shown-01KTNWFC3B1ZGFR9FTT77X7H2Y
  memory/
    058-architectural-review.md
    available_tooling.md
    README.md
    templates/
      POWERSHELL_SYNTAX.md
  metadata.yaml
  migrations/
    mission-state/
      109dbcfa005326f4.json
      22a5a9d3195f1833.json
      73d2ecec75f25774.json
      9f083618f5db308b.json
      cf4abc4ad816579a.json
      e35c2e74babb3f04.json
      quarantine/
        109dbcfa005326f4/
          charter-end-user-docs-828-01KQCSYD/
            status.events.jsonl
          cli-session-survival-daemon-singleton-01KQ9M3M/
            status.events.jsonl
          private-teamspace-ingress-safeguards-01KQH03Y/
            status.events.jsonl
          stable-320-release-blocker-cleanup-01KQW4DF/
            status.events.jsonl
        c680177cc61d4709/
          charter-deadcode-noop-campsite-01KXW0NY/
            status.events.jsonl
          ci-topology-shrink-01KWQAVX/
            status.events.jsonl
          codebase-sanitization-1060-1622-01KV5F0B/
            status.events.jsonl
          docs-ia-onboarding-overhaul-01KY02JB/
            status.events.jsonl
          doctrine-silence-guards-01KYFV7Q/
            status.events.jsonl
          doctrine-tension-edges-01KY1WPC/
            status.events.jsonl
          mission-type-doctrine-authority-01KXH6GE/
            status.events.jsonl
          read-path-error-fidelity-adoption-01KV8NPC/
            status.events.jsonl
          write-side-context-factory-adoption-01KV9W0X/
            status.events.jsonl
  missions/
    01KT6HVH3QND4Q3KCGH2419N4J/
      retrospective.yaml
    01KTDVHZKGCHCW6HQ4V577PNES/
      retrospective.yaml
    01KTSJ2H8E5YF2EGJYGAE5Z5Q2/
      retrospective.yaml
  overrides/
    AGENTS.md
    missions/
      __init__.py
      action_index.py
      documentation/
        command-templates/
          implement.md
          plan.md
          README.md
          review.md
          specify.md
          tasks.md
        expected-artifacts.yaml
        mission.yaml
        README.md
        templates/
          divio/
            explanation-template.md
            howto-template.md
            README.md
            reference-template.md
            tutorial-template.md
          generators/
            jsdoc.json.template
            README.md
            sphinx-conf.py.template
          plan-template.md
          README.md
          release-template.md
          spec-template.md
          task-prompt-template.md
          tasks-template.md
      glossary_hook.py
      models.py
      plan/
        command-templates/
          plan.md
          README.md
          research.md
          review.md
          specify.md
        mission-runtime.yaml
        mission.yaml
        README.md
        templates/
          .gitkeep
          README.md
      primitives.py
      README.md
      repository.py
      research/
        command-templates/
          implement.md
          plan.md
          README.md
          review.md
          specify.md
          tasks.md
        expected-artifacts.yaml
        mission.yaml
        README.md
        templates/
          data-model-template.md
          plan-template.md
          README.md
          research/
          research-template.md
            evidence-log.csv
            README.md
            source-register.csv
          spec-template.md
          task-prompt-template.md
          tasks-template.md
      software-dev/
        actions/
          implement/
            guidelines.md
            index.yaml
          plan/
            guidelines.md
            index.yaml
          review/
            guidelines.md
            index.yaml
          specify/
            guidelines.md
            index.yaml
        command-templates/
          accept.md
          analyze.md
          constitution.md
          dashboard.md
          implement.md
          plan.md
          README.md
          review.md
          specify.md
... 1600 more

Showing a partial view of a very large repo.

FAQ

What is spec-kitty?: Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
How do I install spec-kitty?: Run these in Claude Code: npx -y skills add Priivacy-ai/spec-kitty --agent claude-code. Then prompt normally.
Does spec-kitty auto-invoke its skills?: Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
Is spec-kitty free?: Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.