Phase 02 · Define
Requirements challenger
How it works
Flags weak, ambiguous or contradictory requirements before the build – so teams don't build the wrong thing well.
- Critiques requirements for clarity, testability and scope
- Flags contradictions and gaps – missing NFRs and non-goals
- Delivers a comment thread in the ticket
Roles
Product ManagerProduct Owner
Teklens apps & integrations
JiraConfluence
Example prompts
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Critique requirement [Q] for clarity, testability and scope.
Which NFRs and non-goals are missing from this PRD?
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.