speckit-retrospect-run

Name: speckit-retrospect-run
Availability: InStock
Author: OpsMill

Identify context-management gaps from agent sessions and route findings to follow-ups.

9|4|Updated May 13, 2025

Search Tags:#automation #github #retrospective #spec-kit #code-review #knowledge-management #session-context

Ready to run

npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-retrospect-run

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-retrospect-run
Source: https://github.com/opsmill/infrahub-mcp/tree/main/.agents/skills/speckit-retrospect-run
Command: npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-retrospect-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates structured retrospectives to identify context-management gaps in a session and translate them into actionable follow-ups.

Core Features & Use Cases

Guides a formal retrospective on the current agent session to surface gaps in context provisioning, guardrails, and knowledge surfaces.
Routes findings to approved follow-up actions such as local notes, PRs, or issues.
Supports integration with .specify/ templates and repo governance for debriefs.

Quick Start

Run a retrospective on the current session and generate a structured report with actionable follow-ups.

Frequently Asked Questions about speckit-retrospect-run

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

FAQPage Schema

How do I automate a retrospective to identify context-management gaps in an agent session?▼

Automating a retrospective identifies and catalogs context-management gaps surfaced during an agent session, translating them into structured reports. It analyzes session context provisioning and guardrails to pinpoint missing knowledge surfaces for review.

What is a spec-kit retrospective and how does it route findings?▼

A spec-kit retrospective reviews agent sessions to surface context gaps, routing findings to approved follow-ups like local notes, PRs, or issues. It classifies findings based on repository context to propose actionable development governance tasks.

Do I need a .specify directory to run spec-kit retrospectives?▼

Yes, running retrospectives requires a spec-kit structure containing a .specify directory. You must also grant access to repository context so the system can classify session findings and propose valid follow-up actions.

Can I route retrospective findings directly into GitHub issues and pull requests?▼

Yes, retrospective findings can be routed directly into approved GitHub follow-ups like issues and pull requests. The system classifies context gaps from the session and proposes actionable items within your repository governance.

What's the best way to surface knowledge-management gaps during code reviews?▼

The best way to surface knowledge-management gaps is conducting structured session debriefs that analyze context provisioning. This catalogs missing guardrails and knowledge surfaces, generating actionable notes or issues for repository governance.

Why does the retrospective fail to classify findings without repository context?▼

The retrospective fails without repository context because it relies on repo governance and .specify templates to classify gaps. Access to repository context is required to accurately categorize findings and propose valid follow-up actions.