Retrospective

This skill is guidance, not a script. Learn from the work that happened. Run a retrospective only when requested; finishing a task does not invite an automatic review of the user's process.

When not to use

• Diagnosing a specific defect. Use debug.
• A request to change skills or project policy directly; a retrospective first produces suggestions, not edits.
• A session so short that no method had room to matter.

Inputs and authorization

• Required: the task or period under discussion, and the primary evidence available.
• Authorization: this mode is user-invoked. A retrospective does not automatically authorize edits to skills, project policy, or tooling.

Method

Reconstruct from primary evidence