spk-gate-retrospective

Creates mission retrospectives after merge to surface process learnings and follow-up work.

1.6k|156|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-gate-retrospective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spk-gate-retrospective
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spk-gate-retrospective
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-gate-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a Spec Kitty mission is merged and reviewed, teams often skip capturing what went wrong in the process, so recurring blockers and workflow issues repeat across missions. This skill guides the creation or verification of mission retrospectives so process learnings are recorded without blocking completed work.

Core Features & Use Cases

  • Retrospective Creation: Locates the mission's review and closeout artifacts, then runs or requests retrospective creation when the workflow supports it.
  • Process Learning Summary: Summarizes process issues, recurring blockers, and useful follow-up work for future missions.
  • Separation of Concerns: Keeps product bugs distinct from process improvements so each gets the right follow-up.
  • Use Case: After merging a multi-agent feature mission in Spec Kitty, ask for a retrospective to identify which work packages stalled in review and what workflow changes would prevent it next time.

Quick Start

Ask the agent to create a retrospective for the just-merged Spec Kitty mission and summarize the process learnings.

Frequently Asked Questions about spk-gate-retrospective

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

FAQPage Schema
How do I create a retrospective after merging a Spec Kitty mission?

Invoke this skill after merge and mission review. It locates the mission's review and closeout artifacts, then runs or requests retrospective creation when the workflow supports it, summarizing process issues and follow-up work.

What does a Spec Kitty mission retrospective include?

The retrospective summarizes process issues, recurring blockers, and useful follow-up work from the mission. It keeps product bugs separate from process improvements so each category receives appropriate follow-up.

When should I run a mission retrospective in a spec-driven workflow?

Run it after merge and mission review, or whenever you want to understand what was learned from a mission. It is designed not to block completed work, so it fits naturally at the end of the workflow.

Does the retrospective gate block merging completed work?

No. The skill explicitly surfaces process learnings without blocking completed work. The retrospective is meant to be useful to future missions rather than a rewrite of the change summary.

What are the limitations of a process retrospective versus a code review?

A retrospective focuses on workflow and process learnings, not code correctness. Product bugs and implementation defects belong in review artifacts; the retrospective captures recurring blockers and process improvements for future missions.