Phase 02 · DefineEvent-driven
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
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.
Show all PRDs and stories made inconsistent by the latest schema change.
Related use cases
Three use cases closely connected to this one.
Prioritisation by impact and feasibility.Prioritises features by business impact × technical feasibility – grounded in the real code instead of gut feeling.View use case A roadmap anchored in Jira and code.Connects strategic priorities with Jira, dependencies and real engineering reality – and flags it when the two drift apart.View use case Spec → epic with code contextTurns a spec into a build-ready epic with acceptance criteria from real code paths.View use case
From the PM Lab
Articles that explore this use case in depth.
Give Teklens a real job.
Connect Jira and your code – and let Teklens work on something real.