Phase 02 · Define
Shift-left compliance & security
How it works
Data-protection, compliance, AI-governance and architecture questions become visible on the real code as early as the Define phase – including an anonymisation mode for regulated environments, long before implementation starts.
- Checks planned requirements early for data-protection, legal and AI-compliance risks against the code
- Flags affected components, data flows and legal dependencies before the build
- Runs in anonymisation mode – model choice and CH/EU hosting per project
Roles
CPO / CTO · tech leadershipHead of product & engineering
Teklens apps & integrations
Teklens.aiJiraConfluenceGitHub
Example prompts & actions
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Which data-protection and compliance risks does requirement [Q] have according to the code?
Show the legal and architecture dependencies of [feature] before implementation.
Check [epic] against our AI-governance requirements.
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
Give Teklens a real job.
Connect Jira and your code – and let Teklens work on something real.