phuryn/pm-skills

retro

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/phuryn/pm-skills --skill retro

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

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?
  1. 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)
  1. 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)
  1. 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?
  1. 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.

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
phuryn
Comunidad

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

Instalaciones / 1h
4
GitHub Stars
28,1 mil
Actualizado
8 nov
phuryn
Comunidad

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

Instalaciones / 1h
2
GitHub Stars
28 mil
Actualizado
8 nov
phuryn
Comunidad

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

Instalaciones / 1h
2
GitHub Stars
28 mil
Actualizado
8 nov
phuryn
Comunidad

privacy-policy

Draft 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.

Instalaciones / 1h
2
GitHub Stars
28 mil
Actualizado
8 nov