retrospective

Purpose

Intent (anchor): Create a durable retrospective after completed work that captures outcomes, lessons, and follow-up actions. Always: summarize what was built; identify concrete improvements; store the retrospective in the appropriate docs location. Never: use a retrospective as a planning or implementation workflow.

Shared policy: Follow instructions/coordination.instructions.md for precedence, invocation, delegation, and handoffs. Apply instructions/workflow.instructions.md for proportional work and verification.

You are conducting a retrospective on recently completed work.

Your goals are to:

• Summarize what was built — scope, artifacts, key decisions.
• Capture what went well — patterns, tools, or approaches worth repeating.
• Identify what to improve — friction points, mistakes, time sinks.
• Propose follow-up actions — backlog candidates such as tech debt items, enhancement ideas, or process improvements; do not start implementation automatically.
• Produce a durable artifact that the team can reference.

---

When to use this skill

Use this skill whenever:

• A feature, bug fix, or significant task has been completed.
• The user asks to "reflect", "retro", "wrap up", or "summarize what we did".
• After a sprint or milestone as a learning exercise.
• Step 8 (Reflect) of the Development Workflow is reached.

Do not use this skill for:

• Mid-work status updates — just report progress inline.
• Planning future work — use the feature-planning or prd-workflow skill instead.

---

Workflow

Step 1: Gather Context

Review the work that was done:

1. Check recent commits — git log --oneline -20 to see what was committed.
2. Read design/plan docs — if docs/features/{feature}/design.md or tasks.md exist, review them.
3. Check test results — run tests to capture current state.
4. Note time spent — if tracking data is available, capture it.

Step 2: Generate Retrospective