Agent skill

iterate-retrospective

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.

Stars 133
Forks 19

Install this agent skill to your Project

npx add-skill https://github.com/product-on-purpose/pm-skills/tree/main/skills/iterate-retrospective

Metadata

Additional technical details for this skill

author
product-on-purpose
category
reflection
frameworks
[
    "triple-diamond",
    "lean-startup",
    "design-thinking"
]

SKILL.md

Retrospective

A retrospective is a structured reflection that helps teams learn from their experiences and continuously improve. By regularly examining what went well, what didn't, and what to change, teams build a culture of learning and adaptation. The value isn't just in the discussion—it's in the documented actions and follow-through.

When to Use

  • At the end of every sprint (for agile teams)
  • After completing a significant project or milestone
  • Following a major incident or outage
  • When team dynamics feel off and need addressing
  • At regular intervals (monthly, quarterly) even without specific triggers
  • When onboarding new team members to establish improvement culture

Instructions

When asked to facilitate or document a retrospective, follow these steps:

  1. Set the Context Define what period or project this retrospective covers, who attended, and any significant events that occurred. This frames the discussion and helps future readers understand the context.

  2. Choose a Format Select a retrospective format that fits the team's needs. Common options include:

    • Start/Stop/Continue: Simple and direct
    • 4Ls: Liked, Learned, Lacked, Longed for
    • Mad/Sad/Glad: Emotion-focused
    • Sailboat: Visual metaphor (wind=helps, anchor=holds back)
  3. Gather Input Collect observations from all team members. Ensure everyone contributes—quiet voices often have important insights. Group similar items to identify themes.

  4. Discuss and Prioritize Don't try to address everything. Focus the discussion on the most impactful items. Vote or discuss to identify the top 2-3 issues to address.

  5. Define Action Items Convert insights into specific, assignable actions. Every action needs an owner and a due date. Avoid vague improvements like "communicate better."

  6. Review Previous Actions Check the status of action items from the last retrospective. Celebrate completions and discuss blockers for incomplete items. This builds accountability.

  7. Document for Future Reference Capture the key points so they're available for future team members and for tracking patterns over time.

Output Format

Use the template in references/TEMPLATE.md to structure the output.

Quality Checklist

Before finalizing, verify:

  • All attendees had opportunity to contribute
  • Both positives and improvements are captured
  • Action items have owners and due dates
  • Previous retrospective actions are reviewed
  • Document is useful to someone who wasn't in the room

Examples

See references/EXAMPLE.md for a completed example.

Expand your agent's capabilities with these related and highly-rated skills.

product-on-purpose/pm-skills

init-project

Initialize projects with agentic coding structure. Use when setting up a new project, adding AI agent support to existing project, or when user says "init", "initialize", "setup project", or "scaffold". Creates AGENTS folder, documentation templates, and _NOTES scratch space.

133 19
Explore
product-on-purpose/pm-skills

init-project-jpkb

Initialize new JPKB projects with standardized documentation and folder structure. JPKB-specific version with category folders and fixed base path. Use when creating a new project in the jpkb repository, when the user says "init project", "new project", or when the target is the JPKB projects folder.

133 19
Explore
product-on-purpose/pm-skills

wrap-session

End-of-session documentation workflow that updates README, CHANGELOG, agent context files, and creates session logs. Use when wrapping up a working session, when asked to document session progress, when preparing handoff documentation, or when the user says "wrap up", "end session", "document progress", or "save session".

133 19
Explore
product-on-purpose/pm-skills

skill-template

133 19
Explore
product-on-purpose/pm-skills

utility-update-pm-skills

Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.

133 19
Explore
product-on-purpose/pm-skills

utility-update-pm-skills

Validates internet access, compares the locally installed pm-skills version against the latest public release, and updates local files with conflict-aware overwrite-or-skip options. Produces an update report listing changed files, skipped files, and new capabilities. Use when you want to bring a local pm-skills installation up to date.

133 19
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results