Documentation
Docs in progress.
Full docs are in the works. Until then, the use cases document every capability – with a how-to and example prompts. Or book a demo to see Teklens in your workspace.
Every use case as a how-to
Each use case explains briefly what it does – the detail page shows the steps and example prompts.
01
Discover
- Customer insightsClusters scattered customer signals from every source and turns them into prioritised product opportunities.
- Duplicate & relatedness sweepFinds duplicate and related ideas and bugs across the whole backlog – linked to the code they touch.
- Code-grounded estimationThe first rough triage in Discover: effort, risk and complexity for every incoming idea – estimated against the real code.
- Bug statisticsClusters reported bugs in the backlog and shows where defects pile up – the basis for targeted improvements.
- Stakeholder reports & summary widgetTurns bugs, ideas and customer satisfaction into ready-to-send visual reports – on a single prompt.
- Domain knowledge from the codeNavigates the codebase semantically and extracts product and domain knowledge – new PMs are productive in days, not months.
- Auto-cluster & categorisationClusters, categorises and estimates every new idea, bug or ticket automatically on arrival.
- Vision-fit checkFinds the stories and epics that carry the vision – and the ones that contradict it.
- Feasibility-aware prioritisationPrioritises the portfolio by value AND real difficulty – every initiative annotated with code-anchored effort, risk and impact.
02
Define
- Spec → epic with code contextTurns a spec into a build-ready epic with acceptance criteria from real code paths.
- PRD expertWrites code-grounded PRDs that reference real modules, data and constraints.
- Acceptance criteria & edge casesGenerates acceptance criteria with edge cases from real code paths the moment a story enters refinement.
- Requirement feasibility checkChecks every requirement against the API, schema and test surface of the codebase – before anything is built.
- Requirements challengerFlags weak, ambiguous or contradictory requirements before the build.
- Architecture diagrams & blast radiusRenders architecture diagrams from the code and maps the blast radius of planned changes.
- API-vs-code drift reportFlags every diagram, PRD and story that has drifted from the code – weekly or on schema changes.
- Skill Studio: templates & custom checksRecurring artefacts and checks as configurable skills – epic criteria, security checks, API-change reviews, documentation and compliance requirements, the same every time and traceable.
- Shift-left compliance & securityData-protection, compliance, AI-governance and architecture questions become visible on the real code as early as Define – long before anything is implemented.
03
Build
- Estimation with risk driversThe sprint estimate in Build: LOC, complexity and the dependency graph – with the reason behind every number named.
- Cross-team dependency graphSurfaces dependencies from Jira and code at planning time instead of in week two.
- Ticket organiserMoves tickets into sprints and assigns them to epics automatically – roadmap and Jira stay in sync.
- Jira companionJira stays the source of truth – Teklens sits on top as a companion and answers questions about status, complexity and impact with code context.
- Readiness checkerScores and improves the implementation readiness of tickets before the sprint starts.
- Spec conformance checkChecks on every PR whether the code actually implements the story and PRD – drift is caught before the merge.
- Release notes generatorCreates structured release notes from many tickets in seconds – a 30-minute review instead of 4–8 hours of writing.
- Living docsGenerates living documentation from code and PRDs – support, onboarding and customer docs stay current.
- Marketing videosCreates HTML-based product videos from prompts, scenes and motion profiles – exportable as a standalone player.
- Code-aware test strategyFocuses testing on risky, highly coupled areas – coverage gaps become visible.
- Live sprint progress & risk flagsMakes sprint progress and risks visible in real time – daily course corrections instead of waiting for the retro.
- Sprint memoryPersistent context per story, epic and PR – analyses, decisions and memories stay in the working context instead of getting lost in individual chats.
- Pull request summaryCreates clear summaries of code changes and discussions – for a fast, well-grounded review.
04
Operate
- Incident → commitLinks an incident to the commits and PRs that likely caused it – and the owner responsible.
- Ops assistantTriages support issues with a code-anchored diagnosis and drafts concrete solution proposals.
- Auto-triage & dispatchTriages and dispatches every new support issue automatically – first-response time drops.
- Runbooks & postmortemsGenerates runbooks with root-cause analysis – and turns closed incidents into postmortem drafts.
- Incident clustering & pattern reportClusters current incidents into patterns – recurring problems get addressed instead of re-solved.
- Closed-loop knowledgeFeeds operational signals – incidents, root causes, edge cases – back into the next discover cycle automatically.
- Retro & learnings synthesisCondenses the team's retro insights on an epic into a retro note – input for improvement and discover.