retrospect

Analyze session workflow issues and log actionable feedback with sketches.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/iamacoffeepot/aether --skill retrospect-iamacoffeepot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospect
Source: https://github.com/iamacoffeepot/aether/tree/main/.agents/skills/retrospect
Command: npx skills add https://github.com/iamacoffeepot/aether --skill retrospect-iamacoffeepot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the process of reviewing and categorizing workflow issues from sessions, identifying actionable insights, and logging them effectively.

Core Features & Use Cases

  • Session Retrospection: Offers a structured approach to evaluate workflow efficiency and friction points.
  • Papercut Identification: Categorizes and identifies minor issues that may hinder workflow without extensive debugging.
  • Sketch-based Reporting: Files findings with a visual sketch for better understanding and tracking.

Quick Start

Use the 'retrospect' skill to initiate a session review by saying, "Retrospect my latest project session."

Frequently Asked Questions about retrospect

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

FAQPage Schema
What is papercut analysis in project retrospection?

Papercut analysis in project retrospection identifies and categorizes minor workflow friction points that hinder efficiency without requiring extensive debugging, allowing you to log actionable feedback for continuous improvement.

How do I conduct a project post-mortem using session workflow review?

You can initiate a session workflow review by triggering a retrospection command like "Retrospect my latest project session," which analyzes workflow efficiency, identifies friction points, and files findings with a visual sketch for tracking.

Can I use sketch-based reporting for issue tracking during a project review?

Yes, this session retrospection process files your categorized workflow findings with a visual sketch, conveying insights effectively to ensure better understanding and tracking for project post-mortems.

Does project retrospection require a specific review process to identify workflow issues?

Yes, effective project retrospection requires a review process that includes sketching to convey insights effectively, ensuring that identified workflow friction points are properly classified and logged.

What is the best way to categorize minor workflow issues without extensive debugging?

The best way to categorize minor workflow issues without extensive debugging is using a structured papercut analysis method, which identifies friction points and logs them as actionable feedback for continuous improvement.