plumbeer-skill-backwards

Generates STAR-framework retrospective markdown documents from Claude session history.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/marioplumbeer/skills --skill plumbeer-skill-backwards-marioplumbeer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plumbeer-skill-backwards
Source: https://github.com/marioplumbeer/skills/tree/main/.agents/skills/plumbeer-skill-backwards
Command: npx skills add https://github.com/marioplumbeer/skills --skill plumbeer-skill-backwards-marioplumbeer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a long problem-solving session, the reasoning behind decisions is easily lost. This Skill reconstructs a session into a structured retrospective using the STAR framework (Situation, Task, Action, Result) and writes it to a local markdown file for future reference. ## Core Features & Use Cases - Session Analysis: Reads the full conversation and tool history to extract the inciting problem, goal, key decisions, and outcome without inventing content. - STAR Structuring: Maps session material into Situation, Task, Action, and Result sections, with emphasis on a reasoning narrative rather than a transcript of tool calls. - Approval Gate: Drafts the full document, proposes a dated filename and path, and waits for explicit user approval before writing anything to disk. - Use Case: After debugging a production issue with Claude, ask for a retrospective to capture why each diagnostic step was taken, producing a shareable markdown record for your team. ## Quick Start Ask the assistant to write a retrospective of this session using the STAR framework and save it as a markdown file.

Frequently Asked Questions about plumbeer-skill-backwards

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

FAQPage Schema
How do I document a Claude session as a retrospective?▼

Ask the assistant to write a retrospective of the current session. It reads the conversation history, maps it to the STAR framework (Situation, Task, Action, Result), shows you a full draft for approval, then writes a dated markdown file to your working directory.

What is the STAR framework for session retrospectives?▼

STAR stands for Situation, Task, Action, Result. Situation describes the context before work began, Task states the concrete goal, Action captures the reasoning narrative behind each decision, and Result records what is now true, including open threads.

Does the retrospective skill write files without asking?▼

No. The skill presents the full draft document, proposed filename, and target path, then waits for explicit approval before writing. If you request changes, it revises and re-presents until you approve.

What happens if a retrospective file already exists?▼

The skill appends a numeric suffix like -2 or -3 to the filename rather than overwriting the existing file. This preserves earlier retrospectives written on the same date or topic.

Can the retrospective handle sessions with multiple problems?▼

The skill scopes to one problem thread per retrospective. If the session covered multiple unrelated problems, it asks which thread to document before drafting, keeping each retrospective focused.