Phase 04 · Operate
Retro & learnings synthesis
How it works
After the epic closes, when the team looks back: the insights from the retro are condensed into a structured retro note and linked to code and components – input for improvements and the next discover cycle. The difference to Closed-loop knowledge: there operational signals such as incident root causes flow back automatically; here the team synthesises what it learned itself.
- Synthesises the team's learnings from completed epics
- Links insights to code and components
- Condenses everything into a retro note for the next cycle
Roles
Head of product & engineering
Teklens apps & integrations
Teklens.aiConfluenceJira
Example prompts & actions
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Create a retro note from epic [E].
Related use cases
Three use cases closely connected to this one.
Incident → commitLinks an incident to the commits and PRs that likely caused it – and the owner responsible.View use case Bug triage and resolution without senior capacity.Triages bugs, finds the likely cause in the code and prepares the resolution – or executes it.View use case Auto-triage & dispatchTriages and dispatches every new support issue automatically – first-response time drops.View use case
Give Teklens a real job.
Connect Jira and your code – and let Teklens work on something real.