Loading...
Loading...
Found 59 Skills
Run blameless post-mortems & retrospectives and produce a Post-mortems & Retrospectives Pack (brief + agenda, facts/timeline, contributing factors + root causes, decisions + action tracker, kill criteria, learning dissemination plan). Use for postmortem, post-mortem, retrospective, retro, after action review, lessons learned. Category: Leadership.
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.
Generate LESSONS.md retrospective files that capture institutional knowledge, especially failures. Use when closing out journalism projects, investigations, events, or publications. Includes templates for research projects, event post-mortems, editorial tools, and publications.
Ship, measure, and learn effectively. Use when planning staged rollouts, setting up metrics hierarchies, running bet retrospectives, or executing GTM launches. Part of the Modern Product Operating Model collection.
Use when running meetings, workshops, brainstorms, design sprints, retrospectives, or team decision-making sessions. Apply when need structured group discussion, managing diverse stakeholder input, ensuring equal participation, handling conflict or groupthink, or when user mentions facilitation, workshop design, meeting patterns, session planning, or running effective collaborative sessions.
Trigger: Called when a task is completed, enters phase acceptance, receives critical feedback, or repeated similar errors require systematic correction; common signals include review, audit, retrospective, quality check, error correction and retrospective. Trigger after delivery or at a review checkpoint when quality must be examined honestly and errors must be corrected without defensiveness. Use this skill for structured self-review, feedback processing, and continuous correction.
Expert product launch strategist for SaaS and technology companies. Use when planning product launches, coordinating cross-functional launch teams, managing beta programs, creating launch communication plans, planning launch day execution, setting up post-launch monitoring, running launch retrospectives, or defining launch metrics. Covers launch tiering, internal enablement, rollback planning, and contingency strategies.
Use this tool when you are completing project work and need to extract reusable knowledge from project notes. It is triggered by commands such as "organize assets", "refine", during project retrospectives, or in high-context debugging sessions that reveal valuable patterns. Trigger commands: /asset-refine, /asset-extract
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of sprints, projects, or milestones to reflect and improve team practices.
Extract learnings from completed work. Trigger phrases: "run a retrospective", "extract learnings", "what did we learn", "capture lessons", "create a retro".