Retrospective Analysis Skill

Generate a data-grounded retrospective brief that separates facts from feelings, so the team spends retro time on solutions rather than debating what happened.

Required Inputs

Ask the user for these if not provided:

• Sprint tickets: planned vs. completed
• Carry-over tickets and reasons (if known)
• Tickets reopened after closing (quality signal)
• Any incidents or unplanned work (scope creep signal)
• Sprint velocity vs. historical average (trend context)