speckit-retrospect-run

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.

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.

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.

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.

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.

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.