The spec goes where the work gets built.

An approved story carries task, plan and context. Teklens hands it to your tool by link, opens it in the local checkout or starts a coding agent in an isolated environment. Branch, pull request and Jira link come back.

Beta

Handover chain · TEK-418

Engineering receives

Jira ticket TEK-418 with code context
Linked stories & dependencies
Estimate 6–8h, from the code

Logged · Audit trail #4801

The problem

Context gets lost between the ticket and the editor. Whoever builds re-reads the spec, asks around and makes assumptions nobody approved.

What you can do

Copy the handover instruction with task, plan and context and use it in any agent.
Open the ticket in the local checkout with Claude Code or Codex.
Start Codex or OpenCode as a Teklens agent, with model choice per run.

How it works.

01
Prepare the handover
You pick the Jira ticket. Teklens assembles task, plan and context.
02
Choose the route
A link for your own agent, a local tool, or a Teklens agent in the sandbox.
03
Build
The agent works in the checkout or in the isolated environment and reads the context through the handover link.

From the product

Implementation review per acceptance criterion, with the files involved.

Output and next step

One branch and one pull request per repository, linked in the Jira ticket.

Next: skills and playbook

Availability

Beta

Live for Codex and OpenCode as Teklens agents. Claude Code as a Teklens agent is coming.
Open locally: Claude Code and Codex. Other tools through the handover instruction.
Handover links expire and can be revoked.