Phase 02 · Define
Skill Studio: templates & custom checks
How it works
Recurring artefacts and checks are set up as configurable skills – epic criteria, security checks, API-change reviews, documentation and compliance requirements run the same way and traceably on every matching item, grounded in the real code.
- Configures reusable skills per use case – checklist, template or check
- Grounds every check in the real code – affected APIs, schemas, components
- Delivers reproducible widgets – fit for review and audit processes
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.
Create a skill that checks every new epic against our definition of ready.
Configure a security check for tickets that touch [component].
Set up a PRD template for [product area] with our compliance fields.
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.