Turn conversations into product work.
Teklens sits in your product conversations and turns decisions into product work – connected to Jira and the real code.
Insights from connected sources – Jira, Confluence, files – are live. The meeting bot that follows conversations as they happen is in development.
Today
Decisions, customer feedback and requirements stay stuck in meetings, transcripts and people's heads. Afterwards someone from the product team translates the recording into Jira by hand – and briefs engineering all over again.
With Teklens
- Conversation
- Decision
- Jira
- Code
- Recognises what was decided in the conversation and what is still open
- Checks the existing context: earlier decisions, open tickets, specs
- Reconciles it against Jira and the real code
- Creates or updates the spec and the Jira story, with the affected components
- Proposes the next action instead of filing a summary
Result
An executable Jira story: decision, user insight, related work, affected code and the suggested next action.
Why Teklens?
Because Teklens knows the context behind the conversation – your product, your Jira and the real code.
Roles
Teklens apps & integrations
Example prompts & actions
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Summarise the decisions from the meeting on [date] and show which Jira items they affect.
Turn decision [X] into a Jira story with code context.
Do we already have something like this – in Jira or in the code?
Related use cases
Three use cases closely connected to this one.
Give Teklens a real job.
Connect Jira and your code – and let Teklens work on something real.