Saltar al contenido
Marketplace

retro

de phuryn

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.

Resumen

SKILL.mdLeída en 8607e3b

Sprint Retrospective Facilitator

Run a structured retrospective that surfaces insights and produces actionable improvements.

Context

You are facilitating a retrospective for $ARGUMENTS.

If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.

Instructions
  1. Choose a retro format based on context (or let the user pick):

    Format A — Start / Stop / Continue:

    • Start: What should we begin doing?
    • Stop: What should we stop doing?
    • Continue: What's working well that we should keep?

    Format B — 4Ls (Liked / Learned / Lacked / Longed For):

    • Liked: What did the team enjoy?
    • Learned: What new knowledge was gained?
    • Lacked: What was missing?
    • Longed For: What do we wish we had?

    Format C — Sailboat:

    • Wind (propels us): What's driving us forward?
    • Anchor (holds us back): What's slowing us down?
    • Rocks (risks): What dangers lie ahead?
    • Island (goal): Where are we trying to get to?
  2. If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):
    • Group similar items into themes
    • Identify the most frequently mentioned topics
    • Note sentiment patterns (frustration, energy, confusion)
  3. Analyze the sprint performance:
    • Sprint goal: achieved or not?
    • Velocity vs. commitment (over-committed? under-committed?)
    • Blockers encountered and how they were resolved
    • Collaboration patterns (what worked, what didn't)
  4. Generate prioritized action items:
    PriorityAction ItemOwnerDeadlineSuccess Metric
    1[Specific, actionable improvement][Name/Role][Date][How we'll know it worked]
    • Limit to 2-3 action items (more won't get done)
    • Each must be specific, assignable, and measurable
    • Reference previous retro actions if available — were they completed?
  5. Create the retro summary:
     ## Sprint [X] Retrospective — [Date]

 ### Sprint Performance
 - Goal: [Achieved / Partially / Missed]
 - Committed: [X pts] | Completed: [Y pts]

 ### Key Themes
 1. [Theme] — [summary]

 ### Action Items
 1. [Action] — [Owner] — [By date]

 ### Carry-over from Last Retro
 - [Previous action] — [Status: Done / In Progress / Not Started]

Save as markdown. Keep the tone constructive — the goal is improvement, not blame.

Archivos 1 archivo

Instálala a mano

Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:

npx skills add phuryn/pm-skills --skill retro

Más de phuryn

  • create-prdphurynCreate a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.10.4 k instalaciones en skills.sh0
  • competitor-analysisphurynAnalyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.3,600 instalaciones en skills.sh0
  • business-modelphurynGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.3,500 instalaciones en skills.sh0
  • privacy-policyphurynDraft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.3,200 instalaciones en skills.sh0
  • brainstorm-ideas-newphurynBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.3,100 instalaciones en skills.sh0
Todas las skills de phuryn