Phase 02 · DefineTeklens match: very high
Spec → epic with code context
How it works
A spec becomes a build-ready epic – anchored in the real code, so engineering accepts it without ping-pong.
- Reads the spec from Confluence and the code context from the repo
- Generates acceptance criteria from real code paths and data shapes
- Creates the epic in Jira with affected components and dependencies
- Links stories and flags open quality and edge-case questions
Roles
Product ManagerProduct Owner
Teklens apps & integrations
JiraConfluenceGitHubSlack
Example prompts
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Turn the spec at [link] into an epic with acceptance criteria and code context.
Which components does this spec touch, and how risky is the change?
Generate the stories for epic [epic name], including edge cases.
Related use cases
More use cases from the same phase of the cycle.
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 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.
- Skill files: the next AI skill after promptingRead post
- The anatomy of a Jira ticket for AI product management in agentic engineeringRead post
- Discovery stays human, execution becomes the spec: how product managers work with AI in brownfieldRead post
- The MVP for AI: test the wizard before you build the machineRead post
Try Teklens now
Software product management × code intelligence: your context becomes reasoned priorities and build-ready specs.