skills.rest
Priivacy-ai
Priivacy-aiOFFICIAL
Explore all skills by this author →
GitHub

spk-gate-mission-review

Reviews merged Spec Kitty missions for spec-to-code fidelity, requirement coverage, and drift.

1.6k|156|Updated Oct 9, 2025
Search Tags:#drift detection#post-merge#requirement traceability#mission review#Code review#spec-Driven Development#Spec Kitty
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-gate-mission-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spk-gate-mission-review
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spk-gate-mission-review
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-gate-mission-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a Spec Kitty mission merges, teams lack a structured way to verify that the shipped code actually matches the original spec, plan, and functional requirements, leaving drift and gaps undetected.

Core Features & Use Cases

  • Spec-to-Code Fidelity Check: Compares spec, plan, tasks, work packages, reviews, and merged code to confirm alignment.
  • Requirement Traceability: Traces functional requirements to concrete implementation evidence and flags missing coverage.
  • Risk and Follow-up Detection: Identifies drift, missing tests, security concerns, and produces a final verdict with recorded follow-up issues.
  • Use Case: After merging a multi-agent feature mission, run this review to confirm every functional requirement is implemented, tested, and free of unresolved risks before closing the mission.

Quick Start

Ask the agent to run a mission review on the recently merged Spec Kitty mission and produce a final verdict with follow-up issues.

Frequently Asked Questions about spk-gate-mission-review

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

FAQPage Schema
How do I review a merged Spec Kitty mission?▼

Invoke this skill after a mission merges. It compares the spec, plan, tasks, work packages, reviews, and merged code, then produces a final verdict with recorded follow-up issues.

How to trace functional requirements to code after a merge?▼

The review traces each functional requirement to implementation evidence in the merged code. Requirements without matching evidence are flagged as coverage gaps in the final verdict.

When should I run a mission review in spec-driven development?▼

Run it after a mission has merged, or whenever a user explicitly asks for a mission review. It is designed as a post-merge gate, not a pre-merge check.

What issues does a post-merge mission review detect?▼

It detects drift between spec and implementation, missing tests, security concerns, and uncovered functional requirements. Findings are recorded as follow-up issues alongside the final verdict.

Does spk-gate-mission-review replace spec-kitty-mission-review?▼

No, it acts as a gate-level entry point and references spec-kitty-mission-review as a legacy alias for detailed review mechanics when that skill is available.

Related Skills

Explore More Software Engineering Skills→
stijn-dejonghstijn-dejongh
1

spec-kitty.tasks-packages

Generate work package files from a wps.yaml manifest for Spec Kitty tasks.

Community
Advanced
Rinzler78Rinzler78
1

bmad-retrospective

Analyze completed epic work and story records to identify recurring issues and prepare follow-up actions.

Community
Advanced
MaelwalserMaelwalser

claude-devfleet

Coordinate parallel coding agents across mission DAGs in isolated git worktrees.

Community
Advanced
nok0321nok0321

code-review

Review code for static analysis, security, robustness, structure, and test impact issues.

Community
Intermediate