Live LabsLeadersTransformation2 hours

Write the AI coding playbook for your team

Teams adopt coding agents one engineer at a time, and every engineer invents their own rules. We write the shared rules once, starting from a spec-driven workflow, so speed does not cost you review quality.

You leave with

A two-page playbook: where agents may write code, what needs a spec first, and how review changes.

How the time is spent

  1. I do30 minParam builds it live

    I take one feature from spec to merged pull request with an agent, and show which steps a human owned.

  2. We do48 minTogether, step by step

    We sort a list of real tasks into agent-led, agent-assisted and human-only, and argue the borderline ones.

  3. You do42 minOn your own code

    You draft your team's playbook and swap it with another leader for review.

What you will be able to do

Set the boundaries

Decide where agents write code and where they only suggest.

Keep review honest

Change review rules for agent-written code without slowing everyone down.

Start from a spec

Use spec-driven development so agents build what was agreed.

Starts from

Before you come

For
Engineering managers, tech leads and CTOs rolling out coding agents.
You need
None. Bring one rule your team already argues about.
Stack
Spec Kit, Claude Code, GitHub
Track
Run AI adoption across a team, with numbers you can defend.