Phase 02 · DefineFeatured
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 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.
Try Teklens now
The planning software that knows your business – and turns it into specs, epics and stories grounded in real code context.