New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Spec Kitty Runtime Review

by spec-kitty in spec-kitty/spec-kitty

Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback.

MITAuto-check passedProduct & Project Management

Install Spec Kitty Runtime Review

skills CLI
$ npx skills add spec-kitty/spec-kitty --skill spec-kitty-runtime-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install spec-kitty/spec-kitty spec-kitty-runtime-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/charter/offering/skills/spec-kitty-runtime-review .claude/skills/spec-kitty-runtime-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
spec-kitty-runtime-review
GitHub stars
1.7k
Token cost
~1.5k tokens
SKILL.md length
739 words
Files
2 (incl. references)
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback.

  • Works in 6 steps: Load Review Context → Claim the Work Package → Read the Review Prompt → …
  • Product & Project Management work in your project
  • SKILL.md covers When to Use This Skill, Step 1: Load Review Context, Step 2: Claim the Work Package and Step 3: Read the Review Prompt, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spec Kitty Runtime Review is an agent skill from spec-kitty/spec-kitty. Review 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 implementation". Does NOT handle: setup-only repair requests, direct implementation work, editorial glossary maintenance, or runtime loop advancement.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/review-checklist.md`).

It sits in Product & Project Management. The repository describes itself as: Spec-Driven Development with organizational governance. Specs tell AI agents what to build; Charter governs how they build it. Git-native missions, enforceable workflows, and… The licence is MIT.

When your agent uses it

  • Product & Project Management work in your project

Example prompts

  • “review this work package”
  • “check runtime output”
  • “approve this step”
  • “/spec-kitty-runtime-review”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Load Review Context
  2. Claim the Work Package
  3. Read the Review Prompt
  4. 5: Contract Round-Trip Check
  5. Issue Verdict
  6. Check Downstream Impact

What it can do on your machine

Read from SKILL.md and the folder at commit 4cabb90. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Spec Kitty Runtime Review loads about 1.5k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 113 tokens; SKILL.md has 739 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from spec-kitty/spec-kitty at commit 4cabb90, republished under its MIT licence (© spec-kitty). 739 words, ~1,542 tokens.

Download SKILL.mdSave it as .claude/skills/spec-kitty-runtime-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
spec-kitty-runtime-review
description
Review 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 implementation". Does NOT handle: setup-only repair requests, direct implementation work, editorial glossary maintenance, or runtime loop advancement.

spec-kitty-runtime-review

Operate the Spec Kitty review workflow surface: load review context, claim a work package, read the generated review prompt, and issue an approve or reject transition.

When to Use This Skill

  • Claim a completed work package for review
  • Read the review prompt generated by the review workflow
  • Issue an approval or rejection with structured feedback

Step 1: Load Review Context

bash
spec-kitty charter context --action review --json

The returned text contains governance context. The review prompt (generated in Step 2) includes project-specific acceptance criteria and review guidance from charter.offering — do not restate those rules here.

Step 2: Claim the Work Package

bash
# Claim a specific WP (or omit WP## to auto-select from for_review lane)
spec-kitty agent action review WP## --agent <your-name>

This moves the WP from for_review to in_review and prints the path to a generated review prompt file. Read that path from the command output.

Step 3: Read the Review Prompt

bash
cat <prompt-file-path>

The review prompt contains:

  • Acceptance criteria for this specific WP
  • Git diff commands with the correct base branch (use those, not hardcoded main)
  • Dependency warnings if the WP has downstream dependents
  • WP isolation rules
  • Completion instructions (approve/reject commands)

Follow the review prompt. It is the source of truth for what to check and how to check it. The review criteria come from charter.offering and the WP definition, not from this skill.

If the WP diff includes typed sources, confirm the implementer ran the project's configured compiler/typecheck command, matching CI, and that it is green. A passing test runner does not satisfy DIRECTIVE_030's compiler diagnostics gate. Reject if typecheck was skipped or is red; do not accept a fallback command that masks a compiler failure.

Step 3.5: Contract Round-Trip Check

If the mission ships a kitty-specs/<mission>/contracts/ directory, walk it before issuing a verdict. Contracts pin concrete examples (payloads, CLI invocations, schema fragments, error messages, allowed-value sets) that the implementation must round-trip verbatim. Vocabulary or shape drift here is invisible to spec-level review and surfaces late at mission-review or downstream consumption time.

  1. Enumerate — ls kitty-specs/<mission>/contracts/. If the directory is absent, record a one-line note ("no contracts/ artifact") and skip to Step 4.
  2. Filter — for each contract file, decide whether this WP touches the symbols, payloads, or commands it pins. Skipped files get a one-line note ("orthogonal to WP##").
  3. Walk every concrete example — extract every YAML block, JSON snippet, CLI invocation, schema fragment, and error message in the in-scope contracts. Verify the implementation accepts inputs and produces outputs verbatim: singular vs plural, default values, enum members, exit codes, flag names — all of it.
  4. SSOT cross-check — if a contract pins a closed set (allowed values, registered triggers, enum members), require one assertion that mirrors the runtime constant against its test-side or doc-side copy byte-for- byte. If the WP introduces such a constant without that mirror assertion, reject.
  5. Verdict — any contradiction between the implementation and a contract example is a BLOCKER, cited as contract file:line plus impl symbol. Contracts are spec artifacts, not preferences.
Show full SKILL.md (269 more words)Show less

Step 4: Issue Verdict

Take exactly one action — never "approve with conditions".

Approve (all acceptance criteria met)
bash
spec-kitty agent tasks move-task WP## --to approved --note "Review passed: <summary>"
Reject (acceptance criteria not met)

Write structured feedback to a temp file, then move the WP back to planned:

bash
spec-kitty agent tasks move-task WP## --to planned \
  --review-feedback-file <feedback-file-path> \
  --agent <your reviewer id>

A rejection is an ordinary move: pass your own --agent identity and no --force.

Every blocking finding must map to a specific, verifiable remediation action.

The feedback reference is mandatory, not optional. A rejection moves the WP along a backward "review-rejection" edge, and the status contract requires that edge to carry a rationale: the --review-feedback-file (or --note) you pass is recorded as the transition's review_ref / reason and travels on the event wire. Rejecting a WP to planned/in_progress without a feedback reference or note produces a contract-invalid status event that is accepted locally but silently rejected by hosted sync — so the rejection never propagates. Always attach the feedback file (or a --note) when you reject or send a WP back for rework. The rework agent reads exactly that referenced feedback to know what to fix.

Step 5: Check Downstream Impact

If you rejected and the WP has downstream dependents:

bash
spec-kitty agent tasks status --mission <mission-slug>

Note dependent WPs and include a rebase warning in your feedback.

Review Precedence Rules

  1. Acceptance criteria are the primary gate — a WP meeting all criteria passes even if the reviewer would have done it differently
  2. The review prompt is the source of truth — it contains the specific checks, criteria, and doctrine context for this WP
  3. One clear verdict per review — approve or reject, nothing in between
  4. The reviewer does not implement fixes — feedback must be actionable by the original implementing agent

© spec-kitty, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in src/charter/offering/skills/spec-kitty-runtime-review of spec-kitty/spec-kitty.

  • SKILL.md
  • references/review-checklist.md

Open the folder on GitHubat commit 4cabb90

Compare with similar skills

Spec Kitty Runtime Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Spec Kitty Runtime Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spec Kitty Runtime Review this skillspec-kitty/spec-kitty1.7k—~1.5kAutomated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Game Changing FeaturesopenstatusHQ/data-table-filters2.3k3 repos~2.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Convex Create Componentspokvulcan/poker-planning1148 repos~2.6kAutomated safety check: PassMIT
Self Improving Agentfarm-fe/farm5.6k2 repos~3.3kAutomated safety check: NotesMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed

  • Game Changing Features

    openstatusHQ/data-table-filters

    Find 10x product opportunities and high-leverage improvements.

    2.3k GitHub starsUsed in 3 repos~2.1k tokens
    Product & Project ManagementAuto-check passed

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Convex Create Component

    spokvulcan/poker-planning

    Builds reusable Convex components with isolated tables and app-facing APIs.

    114 GitHub starsUsed in 8 repos~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Self Improving Agent

    farm-fe/farm

    A universal self-improving agent that learns from ALL skill experiences.

    5.6k GitHub starsUsed in 2 repos~3.3k tokens
    Product & Project ManagementAuto-check: notes

  • Weekly Engineering Retro

    garrytan/gstack

    Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from spec-kitty/spec-kitty

All 50 skills in this repo

  • Spec Kitty Setup Doctor

    spec-kitty/spec-kitty

    Install, verify, and recover the modern Spec Kitty 2.0.11+ operating surface.

    1.7k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Spk Doctrine Show Me

    spec-kitty/spec-kitty

    Explain Spec Kitty work with compact, checkable visuals. An agent skill from spec-kitty/spec-kitty.

    1.7k GitHub stars~944 tokensUpdated today
    Auto-check passed

  • Spec Kitty Git Workflow

    spec-kitty/spec-kitty

    Understand 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…

    1.7k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Spec Kitty Glossary Context

    spec-kitty/spec-kitty

    Curate and apply canonical terminology across Spec Kitty missions.

    1.7k GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Spec Kitty Mission System

    spec-kitty/spec-kitty

    Understand 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…

    1.7k GitHub stars~4.3k tokensUpdated today
    Auto-check passed

  • Spec Kitty Orchestrator API Operator

    spec-kitty/spec-kitty

    Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI.

    1.7k GitHub stars~3k tokensUpdated today
    Auto-check passed

Categories

Questions about Spec Kitty Runtime Review

What does Spec Kitty Runtime Review do?

Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Spec Kitty Runtime Review is an agent skill from spec-kitty/spec-kitty. Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback.

When should I use Spec Kitty Runtime Review?

Spec Kitty Runtime Review fits situations like: product & Project Management work in your project.

How do I install Spec Kitty Runtime Review in Claude Code?

Run `npx skills add spec-kitty/spec-kitty --skill spec-kitty-runtime-review -a claude-code`. Or copy the skill folder (src/charter/offering/skills/spec-kitty-runtime-review in spec-kitty/spec-kitty) into .claude/skills/spec-kitty-runtime-review in your project. Claude Code loads it when a task matches its description.

How do I install Spec Kitty Runtime Review in Codex?

Run `npx skills add spec-kitty/spec-kitty --skill spec-kitty-runtime-review -a codex`. Or copy the skill folder (src/charter/offering/skills/spec-kitty-runtime-review in spec-kitty/spec-kitty) into .agents/skills/spec-kitty-runtime-review in your project. Codex loads it when a task matches its description.

Can I use Spec Kitty Runtime Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add spec-kitty/spec-kitty --skill spec-kitty-runtime-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-kitty-runtime-review, .gemini/skills/spec-kitty-runtime-review, .github/skills/spec-kitty-runtime-review and .opencode/skills/spec-kitty-runtime-review in your project.

What does Spec Kitty Runtime Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Spec Kitty Runtime Review is instructions for the agent only.

Does Spec Kitty Runtime Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Spec Kitty Runtime Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Spec Kitty Runtime Review use?

Spec Kitty Runtime Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spec Kitty Runtime Review use?

About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 317 tokens, read only when the agent opens those files.

What are the alternatives to Spec Kitty Runtime Review?

Skills that share tags, products or a category with Spec Kitty Runtime Review: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spec Kitty Runtime Review?

spec-kitty (a GitHub organization) maintains it in spec-kitty/spec-kitty, which has 1,677 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 8, 2026.

Source: spec-kitty/spec-kitty on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.