iterate-retrospective

Ask the assistant to facilitate a retrospective by specifying the period covered and a format such as Start/Stop/Continue or 4Ls. It guides input gathering, prioritization, and produces documented action items with owners and due dates.

It supports four common formats: Start/Stop/Continue, 4Ls (Liked, Learned, Lacked, Longed for), Mad/Sad/Glad, and Sailboat. You select the format that best fits your team's needs before gathering input.

Run retrospectives at the end of every sprint, after major projects or milestones, following incidents or outages, and at regular monthly or quarterly intervals. They also help when team dynamics feel off or when onboarding new members.

Every action item must have a specific owner and due date, avoiding vague items like communicate better. The workflow also reviews previous retrospective actions at the start of each session to build accountability.

The skill documents and structures the discussion but cannot replace live team conversation or guarantee honest participation. Quiet team members still need deliberate encouragement, and sensitive interpersonal issues may require a human facilitator.