Teklens Use Cases & Prompt Library
Use cases mapped onto the cycle Discover → Define → Build → Operate, plus a fast lane for small changes.
The most-used use cases.
Customer insights
Clusters scattered customer signals from every source and turns them into prioritised product opportunities.
Vision-fit check
Finds the stories and epics that carry the vision — and the ones that contradict it.
Feasibility-aware prioritisation
Prioritises initiatives by value AND real difficulty — with code-anchored effort, risk and impact.
Spec → epic with code context
Turns a spec into a build-ready epic with acceptance criteria from real code paths.
Release notes generator
Creates structured release notes from many tickets in seconds — a 30-minute review instead of 4–8 hours of writing.
Ops assistant
Triages support issues with a code-anchored diagnosis and drafts concrete solution proposals.
Discover
Gather scattered signals, cluster them and prioritise against company context. Output: a qualified roadmap of prioritised feature candidates.
Customer insights
Clusters scattered customer signals from every source and turns them into prioritised product opportunities.
Duplicate & relatedness sweep
Finds duplicate and related ideas and bugs across the whole backlog — linked to the code they touch.
Code-grounded estimation
Estimates effort, risk, complexity and the experts involved for every idea — grounded in the real code.
Bug statistics
Bug clustering shows where the product keeps failing — the basis for targeted improvements.
Stakeholder reports & summary widget
Turns bugs, ideas and customer satisfaction into ready-to-send visual reports — on a single prompt.
Domain knowledge from the code
Extracts product and domain knowledge straight from the codebase — new PMs are productive in days, not weeks.
Auto-cluster & categorisation
Clusters, categorises and estimates every new idea, bug or ticket automatically on arrival.
Vision-fit check
Finds the stories and epics that carry the vision — and the ones that contradict it.
Feasibility-aware prioritisation
Prioritises initiatives by value AND real difficulty — with code-anchored effort, risk and impact.
Define
Define top candidates deep against the codebase: code-grounded PRDs, acceptance criteria, edge cases. Output: sprint-ready Jira issues linked to code and requirements.
Spec → epic with code context
Turns a spec into a build-ready epic with acceptance criteria from real code paths.
PRD expert
Writes code-grounded PRDs that reference real modules, data and constraints.
Acceptance criteria & edge cases
Generates acceptance criteria with edge cases from real code paths the moment a story enters refinement.
Requirement feasibility check
Checks every requirement against the API, schema and test surface of the codebase — before anything is built.
Requirements challenger
Flags weak, ambiguous or contradictory requirements before the build.
Architecture diagrams & blast radius
Renders architecture diagrams from the code and maps the blast radius of planned changes.
API-vs-code drift report
Flags every diagram, PRD and story that has drifted from the code — weekly or on schema changes.
Build
Estimate grounded in code, map dependencies, allocate into sprints. Quality gates at every status change instead of a sprint-end surprise.
Estimation with risk drivers
Estimates with LOC, complexity and the dependency graph — and names the reason behind every number.
Cross-team dependency graph
Surfaces dependencies from Jira and code at planning time instead of in week two.
Ticket organiser
Moves tickets into sprints and assigns them to epics automatically — roadmap and Jira stay in sync.
Readiness checker
Scores and improves the implementation readiness of tickets before the sprint starts.
Spec conformance check
Checks on every PR whether the code actually implements the story and PRD — drift is caught before the merge.
Release notes generator
Creates structured release notes from many tickets in seconds — a 30-minute review instead of 4–8 hours of writing.
Living docs
Generates living documentation from code and PRDs — support, onboarding and customer docs stay current.
Code-aware test strategy
Focuses testing on risky, highly coupled areas — coverage gaps become visible.
Live sprint progress & risk flags
Makes sprint progress and risks visible in real time — daily course corrections instead of waiting for the retro.
Pull request summary
Creates clear summaries of code changes and discussions — for a fast, well-grounded review.
Operate
Support with access to code, logs and past fixes. Prioritise bug vs feature request, protect senior capacity — and feed insights back into discover.
Incident → commit
Links an incident to the commits and PRs that likely caused it — and the owner responsible.
Ops assistant
Triages support issues with a code-anchored diagnosis and drafts concrete solution proposals.
Auto-triage & dispatch
Triages and dispatches every new support issue automatically — first-response time drops.
Runbooks & postmortems
Generates runbooks with root-cause analysis — and turns closed incidents into postmortem drafts.
Incident clustering & pattern report
Clusters current incidents into patterns — recurring problems get addressed instead of re-solved.
Closed-loop knowledge
Feeds tribal knowledge and root-cause insights back into the next discover cycle.
Retro & learnings synthesis
Condenses the insights from an epic into a retro note — structured input for improvement and discover.
Fast Lane
The express lane for small changes: short request in, clear goal, working code — no heavy planning phase, still code-grounded.