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
Head of product & engineering
Teklens apps & integrations
JiraConfluence
Example prompts & actions
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
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.