Phase 02 · Define

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

Head of product & engineering

Teklens apps & integrations

Teklens.aiConfluenceGitHubJira

Example prompts & actions

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

Three use cases closely connected to this one.

Prioritisation by impact and feasibility.Prioritises features by business impact × technical feasibility – grounded in the real code instead of gut feeling.View use case A roadmap anchored in Jira and code.Connects strategic priorities with Jira, dependencies and real engineering reality – and flags it when the two drift apart.View use case Spec → epic with code contextTurns a spec into a build-ready epic with acceptance criteria from real code paths.View use case

From the PM Lab

Articles that explore this use case in depth.

Give Teklens a real job.

Connect Jira and your code – and let Teklens work on something real.

Try Teklens Talk to a founder