spec-kitty-runtime-review

Claim work packages and issue approve or reject verdicts with structured feedback.

Updated May 13, 2026
One-click install
npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-runtime-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-kitty-runtime-review
Source: https://github.com/kimprobably/maestro-os/tree/main/.claude/skills/spec-kitty-runtime-review
Command: npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-runtime-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams reliably review runtime-owned outputs and decide whether a work package is ready to approve or should be sent back with actionable feedback.

Core Features & Use Cases

  • Claim a work package for review: Move a WP from for_review to doing and surface the generated prompt file for that specific WP.
  • Follow the governance-driven review prompt: Use the prompt as the source of truth for acceptance criteria, git diff instructions (with the correct base branch), and dependency/isolation guidance.
  • Issue a single structured verdict: Approve with a short summary or reject with remediations tied to verifiable actions, optionally including downstream-impact checks for dependent WPs.

Quick Start

Use the spec-kitty runtime review workflow to claim a completed work package and then approve or reject it based on the acceptance criteria in the generated prompt.

Frequently Asked Questions about spec-kitty-runtime-review

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

FAQPage Schema
How do I review a work package against acceptance criteria and approve or reject it?▼

Work package review involves claiming a package from the for_review lane, evaluating generated outputs against acceptance criteria, and issuing a single approve or reject transition with structured feedback files for rejections.

What is a governance-gated work package review workflow?▼

A governance-gated review workflow enforces structured evaluation of runtime outputs before approval, using charter context loading and prompt-based evaluation to verify acceptance criteria, inspect diffs, and consider dependency impacts.

How do I provide structured feedback when rejecting a work package?▼

Structured feedback for rejected work packages is provided via feedback files containing actionable remediations tied to verifiable actions, optionally including downstream-impact checks for dependent work packages.

Does work package review require checking git diffs against a specific branch?▼

Yes, work package review requires inspecting git diffs against the base branch specified in the generated prompt, which serves as the source of truth for acceptance criteria and dependency guidance.

Can I review multiple work packages simultaneously in the for_review lane?▼

The review workflow claims one specified work package at a time, moving it from for_review to doing, ensuring focused evaluation before issuing exactly one approve or reject transition per package.

What happens to dependent work packages when I reject a runtime output?▼

Rejecting a runtime output can include downstream-impact checks for dependent work packages, with structured feedback files containing remediations tied to verifiable actions to assess downstream dependencies.