1 of 77

hello@getclaimable.com

AGILE + DEVOPS DAYS

2025

Engineer to AI Manager: Plan, Delegate, and Deliver in the Age of Agents

2 of 77

Trevor Richardson

Logan Keenan

Elmin Didic

Jared Griffin

3 of 77

AI

Claimable: An AI Company

PROBLEM

Patient Data

Insurance Criteria

Appeal Letter

Medical Science

The Law

+

=

4 of 77

Majority of our code is written by AI

Most time is spent creating plans & reviewing code

5 of 77

6 of 77

It’s Not Vibe Coding

7 of 77

Sharded prompts reduced task success rates by 39% on average

HTTPS://ARXIV.ORG/PDF/2505.06120

8 of 77

MAKE AN ENDPOINT

MAKE AN ENDPOINT

  • Query Params
  • Authorization
  • Authentication
  • Validation
  • Service Layer
  • Repository Layer
  • Response body
  • Unit Tests
  • Integration Tests

vs

9 of 77

Agentic AI Mindset

How does Agentic AI change the way we think about software development

10 of 77

Managing the Context

Only Giving AI What It Needs to Succeed

11 of 77

PLAN → IMPLEMENT → ?? → ?? REVIEW → PULL REQUEST → MERGE

Delegate

12 of 77

Our AI evolution

Three months of agentic innovation in fifteen minutes

13 of 77

Before Agents

14 of 77

15 of 77

Talk to an LLM

16 of 77

Talk to an LLM

17 of 77

Working side-by-side with an agent

18 of 77

Delegating a whole task

19 of 77

Delegating a whole task

20 of 77

Delegating a whole task

21 of 77

Delegating a whole task

22 of 77

Planning is everything

23 of 77

Planning is everything

24 of 77

Planning is everything

25 of 77

Planning is everything

26 of 77

Planning is everything

27 of 77

Planning is everything

28 of 77

Great! Now I can have my agent do everything, right?

29 of 77

Right?

30 of 77

Not yet

31 of 77

It’s time to talk about...

32 of 77

It’s time to talk about...

Context

33 of 77

Why context matters

Innate Knowledge

Contextual Knowledge

34 of 77

Why context matters

Too many people talking to you

Too long of a discussion

35 of 77

Why context matters

36 of 77

Why context matters

37 of 77

Why context matters

38 of 77

Software Engineers

QA Engineers

Lead Engineers

Product Owners

39 of 77

@programmer

@tester

@planner

40 of 77

Delegating to subagents

@programmer

41 of 77

Delegating to subagents

42 of 77

Delegating to subagents

43 of 77

Delegating to subagents

44 of 77

plan

execute

Review

45 of 77

plan

plan

plan

execute

execute

execute

Review

Review

Review

Managing multiple agents

46 of 77

Workflow

Our current flow today

47 of 77

The Steps

WORKFLOW

Explore & Plan

PR Review

Execute

Test and Review

Review

48 of 77

Explore

  • Find and Read Documentation on the web
  • Learn about the codebase
  • Examine a similar pull request

49 of 77

Explore

50 of 77

Explorer Sub-Agent

  • Comprehensive Discovery
  • Detailed Analysis
  • Connection Mapping
  • Usage Patterns
  • Practical Guidance
  • Structure the Response

51 of 77

52 of 77

/Clear

53 of 77

Plan

  • What’s the goal?
  • How it should be done?

54 of 77

Planner Sub-Agent

55 of 77

Planner Sub-Agent

56 of 77

The Steps

WORKFLOW

Explore & Plan

PR Review

Execute

Test and Review

Review

57 of 77

Review

58 of 77

Review

59 of 77

/Clear

60 of 77

The Steps

WORKFLOW

Explore & Plan

PR Review

Execute

Test and Review

Review

61 of 77

Execute

62 of 77

The Steps

WORKFLOW

Explore & Plan

PR Review

Execute

Test and Review

Review

63 of 77

Execute - Programmer Agent

64 of 77

The Steps

WORKFLOW

Explore & Plan

PR Review

Execute

Test and Review

Review

65 of 77

Test and Review

66 of 77

The Steps

WORKFLOW

Explore & Plan

PR Review

Execute

Test and Review

Review

67 of 77

Pull Request Loop

  • Agent:
    • Create a PR
    • Fix CI checks
    • Fix Comments

68 of 77

The Flow

OVERVIEW

EXPERMENT

Try different flows

  • Test, Code, Commit

Integrate MCP servers

  • Browser MCP
  • Figma MCP

KEEP REFINING

It took us weeks to gain confidence in our prompts and agents and we keep working on them

NOT MUCH CHANGED

These steps mostly follow what we already were doing

  • We just focus more on the plan

69 of 77

Side-Effects

The surprising parts.

70 of 77

SIDE-EFFECTS

Big prs (and a lot of them)

Example: a migration

  • Find ways to own it. See it work.

Just fix it (using @claude)

😳WAT!

71 of 77

SIDE-EFFECTS

Testing mindset

  • Lean into integration tests
  • “Plan them” up-front
  • Near zero effort (once patterns established)

72 of 77

SIDE-EFFECTS

Silos

  • Not throwing code over the wall
  • Knowledge shares
  • Pairing on plans rather than the code

73 of 77

SIDE-EFFECTS

Itch to ship more

  • Waiting for X to finish, why not build Y
  • Side missions maybe a smell? 🤷

74 of 77

SIDE-EFFECTS

Itch to ship more: the gambling mentality

  • Reviewing: trust but verify
  • Writing: know when to eject

75 of 77

Takeaway

Keep using good engineering practices

76 of 77

Time for Questions!

(and stickers)

77 of 77

Interested in learning more?

Let’s chat!  engineers@getclaimable.com

Thank you!