retro

Review sessions for recurring friction and propose durable workspace improvements.

15|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Eigenwise/eigenwise-toolshed --skill retro-eigenwise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/workbench/skills/retro
Command: npx skills add https://github.com/Eigenwise/eigenwise-toolshed --skill retro-eigenwise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review a session for recurring friction and convert those patterns into durable workspace improvements instead of one-off fixes.

Core Features & Use Cases

  • Session Retrospective: Identifies repeated corrections, re-derivations, missing conventions, and manual chores that slowed the current session.
  • Fix Mapping: Chooses the smallest durable remedy, such as a live rule, codebase map update, skill, direct doc edit, or catalog extension.
  • Approval-Gated Changes: Proposes improvements first, then applies only the approved ones with verification.
  • Use Case: After a long debugging session, use this Skill to turn repeated environment setup mistakes into a rule or workspace update so the next session starts cleaner.

Quick Start

Ask the assistant to review this session for recurring friction and propose the smallest durable workspace improvements.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I run a session retrospective to fix recurring workspace friction?

A session retrospective reviews your current work session to identify recurring friction like repeated corrections or manual chores, then proposes the smallest durable workspace improvements to prevent them.

What is the best way to turn repeated coding mistakes into permanent workspace rules?

The best way to turn repeated coding mistakes into permanent rules is mapping each friction pattern to the smallest lasting fix, such as a live rule, codebase map update, or direct edit, applied after approval.

When do I need a friction analysis pass on my development session?

You need a friction analysis pass when you notice repeated corrections, missing conventions, or manual chores slowing a session, ensuring those patterns convert into durable workspace upgrades rather than one-off fixes.

How does fix mapping work when converting session friction into codebase updates?

Fix mapping works by analyzing session friction and choosing the smallest durable remedy for each pattern, such as a live rule, codebase map update, skill, direct edit, or catalog extension to permanently improve the workspace.

Can I review what workspace improvements are proposed before they are applied?

Yes, the process is approval-gated: it first proposes improvements for recurring session friction, then applies only the approved ones with verification to ensure safe workspace tuning.

What types of session friction can be converted into durable workspace improvements?

Types of session friction converted into durable improvements include repeated corrections, re-derivations, missing conventions, and manual chores that previously slowed your workflow and required repeated intervention.