re-frame-pair-improver

To extract friction points from a debugging session, provide the transcript to generate a retrospective. The analysis reconstructs session goals, identifies workflow friction and root causes, and proposes high-leverage product improvements.

Turning a pairing session into actionable GitHub issues involves analyzing the transcript to draft issue templates. The Skill proposes 2-5 prioritized improvements and generates optional issue drafts, but only files them with explicit user approval.

Running a retrospective for a re-frame-pair session requires providing the session transcript or a concise summary. The output delivers structured sections for goals, friction, root causes, improvements, and optional issue drafts.

Session analysis can identify workflow misalignment and missing observability by surfacing wasted effort and friction. It diagnoses symptoms first before proposing fixes, applying guardrails to avoid unnecessary changes to your workflow.

You do not need a full session transcript to generate improvement ideas. Providing a concise summary of the re-frame-pair session is sufficient to extract goals, friction, and root causes for prioritized improvements.

The retrospective output focuses on diagnosis before proposing fixes to ensure symptoms are fully understood. This diagnosis-first guidance applies guardrails to prevent unnecessary workflow changes and surface accurate root causes.