retro
by phurynretro helps facilitate a structured sprint retrospective that turns team feedback into themes, action items, owners, and deadlines. Use retro for Project Management, Agile team reviews, and post-sprint reflection when you need a clear retro guide instead of a generic prompt.
This skill scores 78/100, which means it is a solid directory listing candidate for users who need a structured sprint retrospective facilitator. The repository gives enough workflow detail to help an agent trigger it correctly and run it with less guesswork than a generic prompt, though it is still somewhat light on supporting materials and edge-case guidance.
- Clear trigger and use cases in the frontmatter description, including retrospectives, sprint reflection, and action-item creation.
- Operational workflow is explicit: choose a retro format, group raw feedback into themes, and produce prioritized action items with owners and deadlines.
- The body includes concrete facilitation formats such as Start/Stop/Continue, 4Ls, and Sailboat, which gives agents reusable structure.
- No supporting files, references, or install command are provided, so users have limited evidence beyond the SKILL.md workflow itself.
- The repository appears focused on facilitation guidance rather than deeper automation or tool integration, so value may be narrower for teams seeking data-driven retro workflows.
Overview of retro skill
What retro does
The retro skill helps you run a structured sprint retrospective that turns team feedback into clear action items. It is useful when you need more than a generic prompt: the retro skill guides the conversation shape, groups raw comments into themes, and pushes the outcome toward owners and deadlines.
Who should use it
Use retro for Project Management, Agile team leads, Scrum Masters, product teams, or anyone facilitating a sprint review of what went well, what broke down, and what to change next. It is a good fit when the goal is a usable retro outcome, not just a discussion transcript.
Why it is different
The strongest value of this retro skill is structure. It supports multiple retrospective formats, reads user-provided team data when available, and emphasizes synthesis over chatter. That makes it better suited to repeated team rituals than a one-off “write me a retro” prompt.
How to Use retro skill
Install retro
Install the retro skill in your skills directory with the repo path, then point your agent at the skill content before asking for a retrospective. A typical retro install looks like adding phuryn/pm-skills and selecting pm-execution/skills/retro. Use the skill when your task is to facilitate a session, summarize feedback, or convert sprint notes into next-step actions.
Prepare better input
retro works best when you give it concrete context instead of a vague request. Strong inputs usually include:
- sprint dates or iteration name
- team name and project context
- raw feedback, notes, or survey text
- metrics like velocity, incidents, carryover, or blockers
- the decision style you want: Start/Stop/Continue, 4Ls, or Sailboat
A weak prompt says: “Do a retro.”
A stronger prompt says: “Facilitate a retro for Sprint 42 using Start/Stop/Continue. Here are 18 sticky notes, three incidents, and two recurring blockers. Group themes and end with five prioritized actions, each with an owner and deadline.”
Read these files first
Start with SKILL.md because it contains the facilitation rules and the main workflow. If the skill is extended later, also check any README.md, AGENTS.md, or folder-level references, but this repo currently centers on the main skill file. That means the fastest path to good retro usage is reading the instructions, then adapting them to your team’s format and constraints.
Use it in a practical workflow
A good retro workflow is:
- gather raw team input
- choose a format that matches the team’s maturity
- ask the skill to cluster themes and surface patterns
- convert themes into action items with clear ownership
- review the output for realism before sharing it
If your team is busy, ask the skill to optimize for brevity and decision quality. If the retro is sensitive, ask it to avoid blame language and preserve neutral phrasing.
retro skill FAQ
Is retro only for sprint retrospectives?
No. The retro skill is best for sprint retros, but it also fits post-release reviews, project check-ins, incident reflection, and any team debrief where you need structured learning plus follow-up actions.
Do I need raw notes for retro to work well?
No, but results improve a lot when you provide team notes, survey comments, or metrics. Without input, retro can still create a facilitation outline, but it has less evidence to synthesize and may stay generic.
Is retro better than a normal prompt?
Usually yes when you want consistency. A normal prompt can ask for a retrospective, but the retro skill gives you a reusable structure and a clearer path from feedback to action. That matters most for Project Management workflows where repeatability and accountability are important.
When should I not use retro?
Do not use retro if you need a deep root-cause analysis, a formal incident report, or a conflict mediation script. It is designed for retrospective facilitation, not for legal, HR, or technical incident documentation.
How to Improve retro skill
Give it sharper source material
The better the input, the better the retro output. Include concrete examples instead of impressions:
- “Deployments were delayed twice because QA access was missing”
- “Three people mentioned unclear acceptance criteria”
- “Velocity dipped from 42 to 31 after mid-sprint scope changes”
That level of detail helps the skill identify themes instead of inventing them.
Ask for the right output shape
Tell retro what success looks like. For example, ask for:
- 3–5 themes, not a full transcript
- a short facilitation agenda for a 30-minute retro
- action items with owner, due date, and expected impact
- neutral language that avoids blame
This makes retro more useful for Project Management because the output becomes easier to run with in a real meeting.
Watch for common failure modes
The most common miss is overbroad feedback that produces generic recommendations. Another is asking for too many action items, which weakens follow-through. If the first pass feels vague, tighten the prompt by adding sprint context, evidence, and the number of actions you want. Then rerun retro with those constraints so the next output is easier to execute.