Phase 02 · DefineTeklens match: very high

Architecture diagrams & blast radius

How it works

At planning time, before the decision is made: diagrams are rendered from the code on demand, and an impact map shows what a planned change would touch across components, APIs and tests – design decisions with a visible blast radius. The difference to the API-vs-code drift report: this is about the impact of a planned change; that one continuously audits existing artefacts against the code.

Renders architecture diagrams from the current code
Maps the blast radius of a planned change – components, APIs, tests
Supports design decisions before a single line of code changes

Roles

ArchitectEngineerProduct Manager

Teklens apps & integrations

Teklens.aiConfluenceGitHubJira

Example prompts

Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.

Generate the architecture diagram for module [M] from the code.

What is the blast radius of the planned change [description]?

Related use cases

More use cases from the same phase of the cycle.

Spec → epic with code contextTurns a spec into a build-ready epic with acceptance criteria from real code paths.View use case 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

From the PM Lab

Articles that explore this use case in depth.

Try Teklens now

Software product management × code intelligence: your context becomes reasoned priorities and build-ready specs.

Start the demo Talk to a founder