Teklens logo
DEEN
Back to the Playbook
BuildHandoverBU-01

Start implementation

Open the approved story in the coding environment with branch, context, acceptance criteria and a working setup already prepared, for an engineer or a coding agent.

Product statusBetaEnvironment setup is available. The one-click handover into Claude Code, Cursor, VS Code and IntelliJ is in beta.

Context in4 required inputsJira story with acceptance criteria · Implementation plan · Relevant code and previous decisions
TransformationEngineer + Engineering AgentEnvironment Setup · Code Analysis · Atlassian · Local Files
OutcomePrepared branch and working environment with the context loaded, or an explicit blocker report.Artifact: Jira story

Why it matters

Teklens Agents do not write code. Your engineers and coding agents do. This Activity makes sure they start with the decision, the story and the plan already loaded, and with a repository that builds.

Owner

Engineer

Agent-led

Participants · Agents

Product ManagerEngineering Agent

Trigger

Event-drivenA story is Ready for Build and picked up by an engineer or a coding agent.

Required context

JiraJira story with acceptance criteriaJiraImplementation planCodeRelevant code and previous decisionsCodeRepository setup instructions

Optional context

ConfluencePRD and UI draftFilesExpected tool versionsCodeCI configuration

Skills

Environment SetupCode AnalysisAtlassianLocal Files

Activity steps

  1. 1Prepare the branch and load story, plan, decisions and acceptance criteria into the coding environment.
  2. 2Install the runtimes and tools the repository expects.
  3. 3Verify the build and test baseline.
  4. 4Hand over to the engineer or coding agent and keep the link to Jira.

Output

Prepared branch and working environment with the context loaded, or an explicit blocker report.

Artifacts

Updates: Jira story

What good looks like

  • Uses repository-specific versions.
  • No unnecessary global changes.
  • Build and test baseline recorded.
  • Link back to story and decision preserved.

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

Coding environmentGitHubJira

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.

Deep dives from the AI PM Lab

Articles that explain the thinking behind this Activity.

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.

Book a demoBack to the Playbook