Hands-on AI guides for engineering leads

Each guide takes one problem leads hit when agents write the code, such as slow review or unclear cost, and walks through the fix. Read it here or download the ebook.

Open a guide
  1. AnswersWhat should our repo hold before agents write most of the code?

    Build an AI-Ready Engineering Team

    24 pages, as a PDF and an EPUB.

    Six layers your engineering team writes into the repo and owns. For product and engineering leads.

  2. AnswersHow do we unblock review when agents open most of the pull requests?

    AI Code Review for Engineering Leads

    74 pages, as a PDF and an EPUB.

    Unblock review when agents write the pull requests: one agent PR followed from a baseline to the handover. For CTOs and VPs of Engineering.

  3. AnswersWhat happened when a team actually tried it?

    The newsletter

    Notes on running delivery with agents, including what did not work. Written by the person doing the work.

    Read the issues

Read how we work.

The guides are free and the newsletter is public.

  1. Build an AI-Ready Engineering TeamA hands-on guide to the six layers your engineering team writes into the repo and owns.
  2. AI Code Review for Engineering LeadsA hands-on guide to keeping review fast when agents write the pull requests, followed on one agent PR from baseline to handover.
  3. Context Engineering for Coding AgentsA practitioner's guide to what every agent should read before it writes code, so it stops relearning the codebase.
  4. AI Coding Policy Template for Engineering TeamsA practitioner's template: a fill-in AI-POLICY.md, the agent settings that enforce it and the CI job that proves it.
  5. Measure AI ROI in EngineeringA hands-on guide for CTOs to the numbers a CFO accepts: baseline, full cost, a fair comparison and payback.
  6. The newsletterNotes on running delivery with agents, including what did not work. Written by the person doing the work.Read the issues

Want the six files written for your own repo?

In a 30 minute call we look at one of your repos together and find where your changes wait longest.

Book a demo