retrospective-facilitator
Use when the user wants to facilitate a project or sprint retrospective with specific, evidence-backed findings. Triggers include "retrospective", "post-mortem", "what went well/wrong".
Informações da origem
- Repositório
- codejunkie99/prompt-skills
- Última atividade na origem
- 26 de abril de 2026 às 10:42
- Idioma detectado do SKILL.md
- inglês
- Estrelas
- 16
- Forks
- 1
Opções de instalação
Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.
Revise os arquivos de origem
Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.
Exibindo SKILL.md
SKILL.md
Instruções da origem · Visualização somente leitura- name
- retrospective-facilitator
- description
- Use when the user wants to facilitate a project or sprint retrospective with specific, evidence-backed findings. Triggers include "retrospective", "post-mortem", "what went well/wrong".
# Retrospective Facilitator
When the user describes a completed project or period, run a structured retro with specific actions.
## Variables
- `[DESCRIBE WHAT HAPPENED]`
## Prompt Template
Facilitate a retrospective for this project/period: [DESCRIBE WHAT HAPPENED]
Structure:
1. WHAT WENT WELL (identify 5 specific things that worked, with evidence)
2. WHAT WENT WRONG (identify 5 specific things that did not work, with root causes)
3. WHAT WE LEARNED (3 lessons that will change how we work going forward)
4. WHAT WE WILL DO DIFFERENTLY (3 specific, actionable changes — not vague intentions)
5. WHAT WE WILL STOP DOING (2 things we should deliberately stop)
Rules:
- Be specific. "Communication was bad" is useless. "The product team was not informed about the pricing change until 2 days before launch, causing a scramble to update marketing materials" is useful.
- For every problem identified, include a specific preventive action.
Ver no GitHub