spec-kitty-runtime-review
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.
Best use case
spec-kitty-runtime-review is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using spec-kitty-runtime-review should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/spec-kitty-runtime-review/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How spec-kitty-runtime-review Compares
| Feature / Agent | spec-kitty-runtime-review | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# 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 doctrine — 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 `doing` 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 doctrine and the WP definition, not from this skill. --- ## 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 --force \ --review-feedback-file <feedback-file-path> ``` Every blocking finding must map to a specific, verifiable remediation action. --- ## 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
Related Skills
spec-kitty-setup-doctor
Install, 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 no Spec Kitty context, direct runtime loop advancement, or editorial glossary maintenance.
spec-kitty-runtime-next
Drive the canonical spec-kitty next --agent <name> 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 runtime do next", "advance the mission", "what is the next task", "continue the workflow", "what step comes next". Does NOT handle: setup or repair requests, purely editorial glossary or doctrine maintenance, or direct code review.
spec-kitty-orchestrator-api-operator
Teach 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", "orchestrator contract", "external automation". Does NOT handle: host-internal lane mutation (use the host CLI directly), runtime loop advancement (use spec-kitty next), mission sequencing logic (the mission state machine owns that), or setup/repair diagnostics.
spec-kitty-mission-system
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 resolved through the 5-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior. Triggers: "what missions are available", "how do missions work", "which mission should I use", "explain the mission system", "what is a mission", "change the mission", "mission templates", "step contracts", "action index", "mission procedures". Does NOT handle: runtime loop advancement (use runtime-next), setup or repair (use setup-doctor), governance (use charter-doctrine), or glossary curation (use glossary-context).
spec-kitty-glossary-context
Curate 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 loop advancement, setup or repair requests, agent configuration, or direct code implementation tasks.
spec-kitty-git-workflow
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 pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git workflow", "merge workflow", "rebase WPs", "worktree cleanup", "safe commit". Does NOT handle: runtime loop advancement (use runtime-next), setup or repair (use setup-doctor), mission selection (use mission-system).
spec-kitty-constitution-doctrine
Run constitution interview, generation, context, and sync workflows for project governance in Spec Kitty 2.x. Triggers: "interview for constitution", "generate constitution", "sync constitution", "use doctrine", "set up governance", "constitution status", "extract governance config". Does NOT handle: generic spec writing not tied to governance, direct runtime loop advancement, setup/repair diagnostics, or editorial glossary maintenance.
comprehensive-review-full-review
Use when working with comprehensive review full review
code-review-ai-ai-review
You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C
claude-win11-speckit-update-skill
Windows 11 system management
cc-skill-security-review
This skill ensures all code follows security best practices and identifies potential vulnerabilities. Use when implementing authentication or authorization, handling user input or file uploads, or creating new API endpoints.
Post-Mortem & Incident Review Framework
Run structured post-mortems that actually prevent repeat failures. Blameless analysis, root cause identification, and action tracking.