retro

Included with Lifetime

$97 forever

Use when completed work needs to be recorded as a lore artifact covering what happened, what surprised, what broke, and what drifted. Observation only, not interpretation. Triggers include "let's do a retro", "/retro", "review what happened", "capture what happened", and "write up the session".

Code Review

What this skill does

# Retro

Record what happened. The retro is the witness, not the analyst.

Future sessions will find this via `lore-researcher`. Make it searchable: tag the problem types, technologies, and patterns the session touched. That's what surfaces a retro when someone plans similar work later.

## Stance

The body describes what happened. It does not interpret. Forbidden:

- Analysis vocabulary: `lesson`, `insight`, `we learned`, `takeaway` don't appear in retro output.
- "What went well / what could improve" structure — this trains toward invented best-practice tips that don't survive the next project.
- Padding to fill a template. Five lines or fifty, both valid. Length follows the session.

What happened? What did the plan say versus what actually happened? Where did things get tripped up? What surprised? What dead ends were tried? What context is worth preserving for the next session in this area?

Write it as prose. Use structure only when it helps the reader follow.

## Saving

Read relevant work artifacts first (spec, plan, notes) to reconstruct context before writing. Save to `.lore/work/retros/[descriptive-name].html`. Load `${CLAUDE_PLUGIN_ROOT}/shared/document-schema.md` for the meta tag fields.

Title describes the work, not a takeaway. "Auth-flow rollout" is a title. "Why we should always test migrations" is not. Tags and modules are how `lore-researcher` finds this later — keep them grep-discoverable.

The output is HTML — let the structure reflect the session. A chronological timeline of what happened, visual callouts for surprises or dead ends, and a clear distinction between what the plan said and what actually occurred. Prose is the default; structure only where it helps the reader follow. Inline CSS and JS are fine; no external dependencies.

Files: 1

Size: 2.1 KB

Complexity: 7/100

Category: Code Review

Source: https://github.com/rjroy/vibe-garden/tree/main/lore-development/skills/retro

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts