Back to the Playbook
DefineDE-09
Find code owner
Identify the people with the strongest relevant code history for review, input or ownership of a change.
Product statusAvailable now
Context in3 required inputsFeature or story · Affected code area · Git history
TransformationEngineer + Engineering AgentFind Code Owners · Code Analysis
OutcomeRecommended owner and reviewer list with reasons.Result only
Owner
Engineer
Agent-led
Participants · Agents
Product ManagerEngineering Agent
Trigger
A story, review or issue needs the right technical reviewer or owner.
Required context
JiraFeature or storyCodeAffected code areaCodeGit history
Optional context
FilesCODEOWNERS and team mapCodeRecent contributors
Skills
Find Code OwnersCode Analysis
Activity steps
- 1Locate the affected code.
- 2Inspect ownership and change history.
- 3Rank knowledgeable contributors and explain why.
Output
Recommended owner and reviewer list with reasons.
Artifacts
Result only
What good looks like
- Based on relevant recent evidence.
- Formal ownership is distinguished from practical expertise.
- Reasons are stated.
Quality gate
No human gate before the result is promoted. It stays an Activity result in Teklens until a person decides to use it.
Destination
Teklens onlyJira
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.