spec-kitty.review

Name: spec-kitty.review
Availability: InStock
Author: kimprobably

Verify work package implementations against prompts, acceptance criteria, and owned-file boundaries.

Updated May 13, 2026

Search Tags:#code review #test verification #spec validation #work package review #file ownership boundaries #bulk edit compliance

Ready to run

npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-review-kimprobably

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-kitty.review
Source: https://github.com/kimprobably/maestro-os/tree/main/.agents/skills/spec-kitty.review
Command: npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-review-kimprobably

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

spec-kitty.review helps teams validate that a work package implementation correctly follows its prompt, acceptance criteria, and declared file ownership boundaries.

Core Features & Use Cases

Prompt-driven review: Uses spec-kitty agent context resolve and the authoritative work package review context to ensure the review is grounded in the intended spec.
Subtask-by-subtask verification: Confirms each declared subtask is implemented as specified, including test existence and (for code changes) passing results.
Boundary and guardrail compliance: Detects changes outside owned_files and enforces bulk-edit classification/compliance rules (including occurrence map requirements).

Quick Start

Run a spec-kitty review for the target work package by invoking the review command with the correct mission selector.

Frequently Asked Questions about spec-kitty.review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify a work package implementation matches its spec and acceptance criteria?▼

Spec validation for a work package involves reviewing the implementation against its WP prompt, acceptance criteria, and owned-file boundaries. This process checks each declared subtask for correctness and test coverage to ensure compliance.

What is the best way to enforce file ownership boundaries during code review?▼

File ownership boundary enforcement detects changes outside declared owned_files during a work package review. It flags unauthorized modifications to ensure implementations stay within their assigned scope and guardrails.

How do I validate bulk edit compliance and occurrence maps in a spec review?▼

Bulk edit compliance validation checks occurrence maps and category/exception alignment when the mission change mode is bulk_edit. It ensures the work package changes follow the required classification and mapping rules.

Does work package review check for test existence and passing results?▼

Work package review confirms test existence and passing results for code changes. It assesses each declared subtask individually to verify that test coverage meets the specified acceptance criteria.

How does resolving review context ground the spec validation process?▼

Resolving review context uses the authoritative work package prompt and spec-kitty agent context resolution. This grounds the validation in the intended specification rather than arbitrary review criteria.