Phase 02 · DefineEvent-driven
Acceptance criteria & edge cases
How it works
Acceptance criteria are derived with edge cases from code paths and data shape – defect leakage into QA and prod drops, cost-to-fix stays low.
- Trigger: story enters refinement
- Generates acceptance criteria plus edge cases from real code paths
- Adds a risk check directly in the ticket
Roles
Head of product & engineering
Teklens apps & integrations
JiraTeklens.ai
Example prompts & actions
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Generate acceptance criteria and edge cases for story [S].
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.