Phase 02 · DefineEvent-drivenTeklens match: very high
API-vs-code drift report
How it works
The continuous audit of existing artefacts: weekly, or on schema and PR changes, diagrams, PRDs and stories that have become inconsistent with the code are flagged. The difference to Architecture diagrams & blast radius: there you assess the impact of a planned change at planning time; here what is already documented is continuously checked against the code.
- Trigger: code or schema change, PR on a public API – or weekly
- Detects architecture and API drift
- Flags affected PRDs and stories – including what exactly drifted and what its impact is
Roles
ArchitectEngineerProduct Manager
Teklens apps & integrations
Teklens.aiConfluenceJira
Example prompts
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Show all PRDs and stories made inconsistent by the latest schema change.
Related use cases
More use cases from the same phase of the cycle.
Spec → epic with code contextTurns a spec into a build-ready epic with acceptance criteria from real code paths.View use case PRD expertWrites code-grounded PRDs that reference real modules, data and constraints.View use case Acceptance criteria & edge casesGenerates acceptance criteria with edge cases from real code paths the moment a story enters refinement.View use case
From the PM Lab
Articles that explore this use case in depth.
Try Teklens now
Software product management × code intelligence: your context becomes reasoned priorities and build-ready specs.