retro

To generate a structured retrospective for an Obsidian vault, run the /retro command at the end of a session. It creates a standardized note with frontmatter metadata and sections for What Went Well, What Didn't Work, Key Learnings, and Process Improvements.

Capturing key learnings and process improvements is best handled by generating a session retrospective. This approach analyzes outcomes and saves candid feedback into a structured vault note with backlinks to the source session for traceability.

This retrospective workflow requires no external dependencies or components. It operates natively to generate post-mortem notes and stepwise prompts within your existing knowledge-management setup.

Yes, you can use this tool for project post-mortems and learning captures within your vault. It applies across end-of-session reviews and saves standardized notes with backlinks to the original project context.

A standardized session retrospective note includes sections for What Went Well, What Didn't Work, Key Learnings, and Process Improvements. It also satisfies frontmatter metadata requirements to organize reflections within the vault.

You should run a session retrospective at the end of a session when you want to reflect on session quality and outcomes. It uses stepwise prompts to gather candid feedback and generate actionable process improvements.