Phase 02 · DefineEvent-drivenTeklens match: very high
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
Product ManagerProduct Owner
Teklens apps & integrations
JiraTeklens.ai
Example prompts
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
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 Requirement feasibility checkChecks every requirement against the API, schema and test surface of the codebase – before anything is built.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.