Immerse · The Gnar Company 4 weeks · your own work
The Gnar Company

Immerse

The Agentic Fluency Bootcamp

For software engineers, marketers, QA engineers, designers, data engineers, founders, engineering leads, sales, product managers — and skeptics.

Take the assessment ~10 minutes

We’ve been in the trenches with these tools on real client work — the dead ends, the rewrites, and the handful of practices that actually held up under a deadline. Immerse hands that over directly, on your own work rather than a toy repo.

Four Ds, four bands

How your practice deepens

Fluency is not one number. You sit somewhere on each of the Four Ds — and you can be further along on one than another. That is the whole grid: four rows, four bands.

PlanDescriptionThe setup you write — what the work is, how precisely it is specified, and what the agent can see and reach when it starts.
ActDelegationThe latitude you grant — what you hand off versus keep, at what scale, and how freely it runs.
VerifyDiscernmentThe quality you check — how you decide that what came back is actually right, not just plausible.
Across all threeDiligenceThe responsibility you keep — safety, cost, recovery, and who is accountable when it lands wrong. Not a stage: the question asked at every stage.
The four bands
Craftyour own hands
Directa session
Systematizea workflow
Orchestratea fleet
Craftyour own hands
The engineering judgment you already have — specs, review, ownership — with no agent in the loop. Not a deficit: it is the floor every band above is built out of, and the reason the program works on real material.
Directa session
You work an agent live and stay in the loop — a plan reviewed before it runs, a context file it reads every time, output met with targeted skepticism, and a deliberate answer to how much latitude it gets. The unit of work is one session.
Systematizea workflow
The session becomes something you no longer have to think about — recurring work packaged as reusable skills, tools and data sources wired in, scoped sub-work dispatched with real interfaces, and verification you would stake a decision on. The unit of work is a workflow.
Orchestratea fleet
More than one thing at once, under policy you set — parallel and background agents across isolated scopes, automated evals gating output before it reaches you, and cost and accountability owned across the whole. The frontier: the program exposes it so you can decide whether it is worth it for your work, not so you can perform it.
The weekly rhythm

Four weeks

Two weeks of cohort-wide workshops on the material every discipline shares, then two weeks of clinics and twice-weekly 1:1s where the work gets specific to you. One mentor, 3–5 mentees, split two weeks and two.

The sessions
Week 12 workshops · office hoursDirect
Workshop 1The Agentic Loop

Plan, Act, Verify — and ownership as the question asked at every stage. One honest lap, run live, then you write your own workflow out as a formal process.

You leave with: your own work mapped into the three stages.
Workshop 2Context, and why an agent needs it

Watch a real process fail to survive being handed to someone else — then write what was missing into a file, and use it before you leave the room.

You leave with: your workflow's context, written and used.
Week 22 workshops · office hoursDirectSystematize
Workshop 3Latitude, and how you would know

You can safely hand over exactly as much as you can check. Latitude is a setting, not a posture — so this one happens in your own editor.

You leave with: one step's latitude, and a rule that holds.
Workshop 4From a lap to a workflow

Systematize opens while the room is still together. The workflow you have been building for three weeks becomes a skill — a real file you can call by name.

You leave with: your workflow packaged as a skill, and invoked.
Week 32 clinics · 2 × 1:1Systematize
Clinic 1Verification that is independent

Topics: the three ways a verifier stops being independent, reviewer subagents, and what a check still cannot see.

You leave with: a reviewer that is not the author, and a named gap.
Clinic 2Isolation, then running more than one

Topics: git worktrees, what a subagent isolates, skills versus scripts, and one workflow run end to end.

You leave with: a workflow you read before you approved it.
Week 42 clinics · 2 × 1:1Orchestrate
Clinic 3What holds when you are not watching

Topics: sandboxes and what they do not relax, stopping conditions, and hooks that enforce rather than ask.

You leave with: a rule the model cannot decline.
Clinic 4The whole month, in review

Topics: the loop, context, latitude, skills, verification, isolation, workflows, enforcement, orchestration.

You leave with: the through-line, and where your team takes it next.

Interested in running Immerse for your team? Contact us →

Where does your practice live?

Take the Immerse self-assessment — a few minutes for a straight read on where you sit across the Four Ds. Calibration, not a grade.

Take the assessment