speckit-opsmill-retrospect

Runs a session retrospective that classifies context-management gaps into approved follow-up actions.

9|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-opsmill-retrospect-opsmill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-opsmill-retrospect
Source: https://github.com/opsmill/infrahub-solution-ai-dc/tree/main/.agents/skills/speckit-opsmill-retrospect
Command: npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-opsmill-retrospect-opsmill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an agent session, friction caused by missing instructions, stale documentation, or architectural issues is often forgotten instead of being captured as concrete repository improvements. This Skill closes that loop by turning session struggles into approved fixes, PRs, GitHub issues, or local notes. ## Core Features & Use Cases - Structured Finding Classification: Organizes session friction into four categories: instructions/configuration gaps, documentation gaps, architectural friction, and mistakes with corrections. - Disposition Routing: Assigns each finding to fix-now, open-pr, github-issue, or local-only buckets with guardrails that prevent auto-applying risky changes like schema migrations or CI/CD edits. - Approval-Gated Execution: Stays read-only until the user approves the report and each disposition bucket, then saves the retrospective to the spec-kit feature directory or a timestamped ad-hoc path. - Use Case: After a long coding session where the agent repeatedly misread AGENTS.md guidance and rediscovered a workflow, run the retrospective to produce a findings table, get a small doc fix applied immediately, and file a GitHub issue for the larger architectural concern. ## Quick Start Ask the agent to run a retrospective on the current session and route the findings to the appropriate follow-up actions.

Frequently Asked Questions about speckit-opsmill-retrospect

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

FAQPage Schema
How do I run a retrospective on an AI agent coding session?▼

Invoke the retrospective command while the session context is still fresh. The skill reviews the conversation and repository context, classifies friction into four finding categories, and presents a report for approval before taking any action.

What kinds of findings does a session retrospective capture?▼

It captures instructions and configuration gaps in files like AGENTS.md and CLAUDE.md, documentation gaps in dev knowledge and guides, architectural friction needing ADRs or refactors, and mistakes with the guardrails that would have prevented them.

Does the retrospective skill require a spec-kit project structure?▼

It works best inside a spec-kit feature, where it saves the report to the feature directory. Outside spec-kit it falls back to an ad-hoc mode, saving timestamped reports under .claude/retrospectives/.

Can the retrospective apply fixes automatically without approval?▼

No. The skill stays read-only until you approve the report and specific disposition buckets. Ask First topics like schema migrations, dependencies, and CI/CD changes are never auto-applied and are routed to PRs or issues.

Where are retrospective reports saved?▼

Reports go to specs/<current-feature>/retrospective.md for active spec-kit features, or .claude/retrospectives/ with a timestamped filename for ad-hoc sessions. Existing files are never overwritten; a numeric suffix is appended.