Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/Priivacy-ai/spec-kitty/tree/main/src/doctrine/skills/spec-kitty-runtime-review
SKILL.md
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
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
# 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
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)
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:
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:
spec-kitty agent tasks status --mission <mission-slug>
Note dependent WPs and include a rebase warning in your feedback.
Review Precedence Rules
- Acceptance criteria are the primary gate — a WP meeting all criteria passes even if the reviewer would have done it differently
- The review prompt is the source of truth — it contains the specific checks, criteria, and doctrine context for this WP
- One clear verdict per review — approve or reject, nothing in between
- The reviewer does not implement fixes — feedback must be actionable by the original implementing agent
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
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-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-implement-review
Orchestrate 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 WPs", "run the implement-review loop", "orchestrate WP implementation", "dispatch agents for WPs", "coordinate implement and review", "sprint through WPs". Does NOT handle: specify/plan/tasks phases, setup or repair, glossary maintenance, or direct code editing by the orchestrator.
spec-kitty-charter-doctrine
Run 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: "interview for charter", "generate charter", "sync charter", "use doctrine", "set up governance", "charter status", "extract governance config", "load doctrine", "agent profile", "DoctrineService", "action index". Does NOT handle: generic spec writing not tied to governance, direct runtime loop advancement, setup/repair diagnostics, or editorial glossary maintenance.
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.
ad-hoc-profile-load
Load an agent profile on demand to adopt a specific role for the current session. Applies the profile's identity, governance scope, boundaries, and initialization declaration without requiring a running mission. Triggers: "act as the architect", "load the reviewer profile", "switch to implementer", "use the researcher persona", "start a session as planner", "adopt the curator role", "initialize profile", "assume the designer identity". Does NOT handle: mission advancement (use runtime-next), charter interview/generation (use charter-doctrine), or profile creation (use spec-kitty agent profile create).
Didn't find tool you were looking for?