interview-session

Replay a closed Claude Code session and conduct a structured retrospective interview.

8|1|Updated Jul 16, 2013
One-click install
npx skills add https://github.com/844196/dotfiles --skill interview-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-session
Source: https://github.com/844196/dotfiles/tree/main/files/dot_claude/exact_local-marketplace/exact_session/exact_skills/exact_interview-session
Command: npx skills add https://github.com/844196/dotfiles --skill interview-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This service helps teams restart a completed Claude Code session and perform a structured retrospective interview to uncover root causes, capture actionable feedback, and improve future performance.

Core Features & Use Cases

  • Structured retrospective: Reopen past sessions and guide participants through reflective questions to identify failures and improvement opportunities.
  • Participant-perspective insights: Collect feedback from the user’s point of view to inform process changes and tooling.
  • Deterministic prompts and safety: Supports consistent questioning without invoking the model to ensure safe, repeatable results.

Quick Start

Invoke interview-session with a session-id to start the retrospective interview.

Frequently Asked Questions about interview-session

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

FAQPage Schema
How do I conduct a retrospective on a closed Claude Code session?

The retrospective process works by identifying and replaying a closed Claude Code session to conduct a structured interview. It applies deterministic analysis to uncover failure causes and collect actionable feedback from the participant's perspective without invoking the model.

Can I collect participant-perspective feedback without invoking the model?

Yes, participant-perspective feedback is collected without model invocation. The skill operates deterministically with safe prompts to ensure repeatable interviews and consistent questioning across sessions, preventing non-deterministic model behavior during the retrospective.

What is the best way to identify failure causes in past AI coding sessions?

The best way to identify failure causes is performing a structured retrospective on the closed session. By replaying the session and guiding participants through reflective questions, you can uncover root causes and gather actionable feedback to improve future performance and process changes.

How do I start an interview session for process improvement?

To start an interview session for process improvement, invoke the skill with a specific session-id. This reopens the past Claude Code session and guides participants through reflective questions to identify failures and improvement opportunities for future tooling.

Are there limitations to using deterministic prompts for session interviews?

The limitation of using deterministic prompts for session interviews is the lack of dynamic model invocation. While this ensures safe and repeatable results, it restricts the retrospective to structured, predefined questioning without adaptive follow-up generation based on participant responses.