All products

Run a team retrospective with AI

Review what helped or delayed delivery, then turn the evidence into a few changes the team can try and revisit next time.

Run a team retrospective with AI around an event people can recall. A catalogue was ready on Tuesday, yet the printer waited until Friday because nobody knew who could approve the proof. The conduct-retrospective skill helps the team turn that delay into a specific change it can test on the next job.

Bring one success as well. If a new naming convention saved the designer an afternoon of matching product photographs, that is a practice worth keeping. Record what happened and leave room for uncertainty about why.

What it does

  • Review delivery notes and previous actions for the period.
  • Separate evidence of a process problem from speculation about individuals.
  • Identify a successful practice and the observation that supports it.
  • Give each agreed change an owner, due date and success check.
  • Revisit the outcome before adding another improvement to the backlog.

Install and use

  1. Install the skill in your agent and provide authorised project notes or aggregate delivery figures. No separate service is needed.
  2. Ask for a review of the print approval delay, one successful handoff and no more changes than the team can handle next cycle.
  3. Confirm owners and dates with the people involved, then keep the actions where the team can review them.

FAQ

Source

Made by Philipp Thoss. Original skill: conduct-retrospective, published on GitHub under the MIT licence.

View on GitHub