IMPLEMENTATION-RETROSPECTIVE.md

semantic-links	skill-links related-artifacts write-markdown-docs docs/templates/ISSUE.md .github/skills/dev/planning/create-issue/SKILL.md

Implementation Retrospective — {Issue or Work Title}

Create this concrete artifact only as lowercase implementation-retrospective.md inside a folder-style issue specification.

Purpose

Record evidence-based process improvements discovered while implementing {issue/work reference}. This is a blameless review of the implementation approach; it does not replace acceptance-criteria verification or require a retrospective for routine work without material discovery.

Outcome

Summarize the delivered behavior, validation evidence, and the final design.

What Went Well

1. {Practice or decision that produced a useful result.}
2. {Practice or decision that produced a useful result.}

What Changed During Implementation

Describe the material findings, including unexpected constraints, invalidated assumptions, or design changes. Link evidence such as tests, logs, or commits.

Root Cause

Explain which missing or incomplete assumption in the plan, specification, or implementation approach allowed the discovery. Focus on system/process causes, not individual blame.

Improvements for Future Work

1. {Specific, reusable specification, skill, agent, template, or process improvement.}
2. {Specific, reusable specification, skill, agent, template, or process improvement.}

Avoiding Overcorrection

State which additional rules or abstractions are not justified by the evidence.

Evidence

• {Issue specification or task reference}
• {Relevant design/refactor plan}
• {Tests, validation logs, PR, or commits}