hyper-retro

Records a dated reflection of your work and automatically routes it to your specified Obsidian vault and GitHub repository.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyper-retro
Source: https://github.com/galatanovidiu/hyper7/tree/main/skills/hyper-retro
Command: npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runs a retrospective on recent Hyper work and captures what worked, what didn't, and what to change next time, scoped to a specific task or to the project overall.

Core Features & Use Cases

  • Task-scoped retros: write retro.md inside a specific task folder to document lessons learned from that task.
  • Project-scoped retros: append to .hyper/retro.md to capture insights across multiple tasks.
  • History preservation: retros are appended rather than overwritten to maintain a long-running learning record.

Quick Start

Ask for a reflection after completing a task, and let the system append a dated retro to the appropriate location.

Frequently Asked Questions about hyper-retro

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

FAQPage Schema
How do I capture lessons learned after completing a task?

You capture lessons learned by running a retrospective that appends insights to a retro.md file. The system adds a dated entry documenting what worked, what didn't, and what to change next time.

What is a task-scoped retrospective and how does it work?

A task-scoped retrospective writes a retro.md file directly inside a specific task folder to document lessons learned from that individual task.

How do I document project-level insights across multiple tasks?

You document project-level insights by appending reflections to a shared .hyper/retro.md file, which maintains a long-running learning record across multiple tasks.

Do I need any extra tooling to run a retrospective on my workflow?

No extra tooling is required to run a retrospective. The system stores outputs as plain text Markdown files in an append-only format, relying solely on standard text files.

Does the retrospective format overwrite previous history?

No, the retrospective format does not overwrite history. Retros are appended rather than overwritten to preserve a long-running learning record over time.