Phase 02 · Define
PRD expert
How it works
Writes PRDs from proven templates that reference real modules, data and constraints – refinement closes in a single session.
- Generates PRDs that reference actual modules, data and constraints
- Uses reusable, code-anchored templates per product area
- Links every requirement to code, tests and components
Roles
Head of product & engineering
Teklens apps & integrations
Teklens.aiConfluenceJira
Example prompts & actions
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Write a code-grounded PRD for epic [E].
Which modules and endpoints does this requirement touch?
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.