Phase 03 · BuildEvent-driven
Spec conformance check
How it works
Every PR is checked against the story and the PRD it claims to implement – drift is caught before the merge. Done means done, and it reveals where the Jira status and the code reality drift apart.
- Trigger: PR opened or merged
- Checks the implementation against PRD and ADR
- Verifies that a merged PR implements its story
- Reveals where the Jira status and the code reality drift apart
- Delivers a conformance report
Roles
Head of product & engineering
Teklens apps & integrations
Teklens.aiJiraGitHub
Example prompts & actions
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Check story [S] against PRD/ADR.
Does the merged PR [link] implement its story?
Is ticket [ID] really ‹done› according to the code?
Related use cases
Three use cases closely connected to this one.
Estimation with risk driversThe sprint estimate in Build: LOC, complexity and the dependency graph – with the reason behind every number named.View use case Cross-team dependency graphSurfaces dependencies from Jira and code at planning time instead of in week two.View use case Ticket organiserMoves tickets into sprints and assigns them to epics automatically – roadmap and Jira stay in sync.View use case
From the PM Lab
Articles that explore this use case in depth.
- Skill files: the next AI skill after promptingRead post
- Discovery stays human, execution becomes the spec: how product managers work with AI in brownfieldRead post
- The EU AI Act for product managers: compliance as a design principle, not a brakeRead post
- Why Spotify's product management won't work for your business – even less so with AI agentsRead post
Give Teklens a real job.
Connect Jira and your code – and let Teklens work on something real.