Loading...
Loading...
Found 83 Skills
Run blameless post-mortems and retrospectives: Pack with brief, timeline, contributing factors, root causes, action tracker, kill criteria, dissemination plan. Use for postmortem, retro, after-action review, lessons learned. NOT for non-review meetings (use running-effective-meetings), shipping process design (use shipping-products), engineering culture (use engineering-culture), or future risk planning (use planning-under-uncertainty). Category: Leadership.
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.
Portfolio retrospective skill for capturing lessons learned, process improvements, and organizational learning across completed projects.
AI SDLC evidence-backed retrospective workflow. Use when delivery work is complete or paused and an AI assistant needs to capture observations, connect them to validation or artifact evidence, formulate reviewable process or policy improvement proposals, assign ownership, and preserve the rule that policy changes require an accepted decision. Supports `--quick-flow` for focused learning and `--full-flow` for strict evidence and decision gates.
Automated retrospectives — captures learnings at EPIC completion and on manual invocation. EPIC-scoped retros embed a Retrospective section in the EPIC artifact. Cross-epic and time-based retros produce standalone retro docs. Triggers on: 'retro', 'retrospective', 'post-mortem', 'lessons learned', 'debrief', 'what worked', 'what didn't work', 'what did we learn', 'reflect', or automatically after EPIC terminal transitions.
Final retrospective and self-assessment for participants of Claude Code Lab. Runs four sequential interactive parts — progress audit, best prompt, monthly plan, and feedback — using AskUserQuestion. Triggers on "/lab-retro", "lab retrospective", "claude code lab final", or after completing the 6-week Claude Code Lab cohort.
Session retrospective and codification. Run at the end of any significant session to extract learnings, update documentation, and create artifacts that make future sessions smoother. Invoke when: - Finishing a multi-step implementation - After debugging a hard problem - End of any session with 3+ tool calls - "what did we learn?" / "wrap up" / "done" Subsumes /codify-learning (codification is one output, not the only one).
After an agentic task completes, perform a retrospective analysis across 6 dimensions (goal alignment, efficiency, decision quality, error handling, communication, reusability). Score performance, identify inefficiency patterns, evaluate skill usage, and produce actionable improvement recommendations. Triggers on "how did it go", "retrospective", "review performance", "what could be better", or after any long agentic task completes.
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
Create session retrospective with AI diary and lessons learned. Use when user says "rrr", "retrospective", "wrap up session", "session summary", or at end of work session.
Generates a detailed project explanation and retrospective (FOR_USER.md) to help the user learn from the project. Use this skill when the user asks to explain the project, asks "what did we just build?", or invokes the skill to generate a learning resource after a coding session.
Analyze git commits within a specified time range and generate a work retrospective report. Trigger words: retrospective, review commits, git review, what did I do today, work summary, daily review, retrospective