Coding agents become more reliable when the system around them controls context, execution, verification and delivery. In this session I walk through the six layers of a Software Factory (Boundary, Context, Skills, Execution, Verification and Delivery) and show why routing the right context to each task beats writing an ever-longer prompt. You leave with a map to apply to your own codebase.
Watch the recording
The whole session is free on Maven. Sign up with your email and the recording opens.
A coding agent is only as reliable as the system around it. Between the request and the pull request sit six layers, and each one removes a kind of rework.
Request
Boundary
Context
Skills
Execution
Verification
Delivery
Pull request
LayerWhat it doesWhat it stops
Boundary
Sets what the agent may touch: which files, which commands, which network.
What it stops: An agent editing files outside its task, or running a command it should never run.
Context
Routes the architecture, past decisions and team rules a task needs to the agent working on it.
What it stops: Code that compiles and ignores how your codebase works.
Skills
Keeps engineering know-how in reusable skills, written once and used by every agent.
What it stops: The same instructions pasted into every prompt, drifting apart.
Execution
Runs each task in its own Git worktree, inside the boundary.
What it stops: Two tasks colliding, or an agent changing the branch you are working on.
Verification
Checks the work with static gates, holdout tests and a Doer and Tester loop that sends failures back with the reason.
What it stops: Code that looks right reaching your review.
Delivery
Opens the pull request only when every check passes, for an engineer to merge.
What it stops: A bad pull request that costs the team its trust in the agent.
Why this matters
Coding agents write more code than any team can review. Teams that get reliable results do not write longer prompts; they build a system around the agent that controls what it sees, where it runs, how its work is checked and how it ships. This session maps that system so you can find the layer your setup is missing.
What you will learn
Map the six layers of a Software Factory
See what each layer does and which problem it removes from your daily agent work.
Route context to each task
Work out what an agent needs for a task and where that context should come from.
Separate skills from prompts
Keep reusable engineering know-how out of one-off prompts so every agent can use it.
Find the missing layer in your setup
Identify the gap that is causing rework when agents write code for you today.
The ideas behind it
Six layers
Boundary, Context, Skills, Execution, Verification and Delivery: the parts between a request and a merged pull request.
Routed context
Each task gets the files and rules it needs, instead of one ever-growing prompt.
Skills, not prompts
Reusable, reviewed instructions for a kind of task, loaded only when needed.
The series, in order
Each session builds on the one before. Start anywhere: every recording stays on Maven.
Design a Software Factory for Your Coding AgentsAll six layers
Engineers who use coding agents every day and spend too long fixing what they write, and tech leads deciding how agents fit the team's workflow.
You need
None. It helps to have used Claude Code, Codex or Cursor on a real codebase.
Price
Free on Maven. You sign up with your email.
Can't make it live?
The recording is on Maven.
Questions
Does this only apply to Claude Code?
No. The layers apply to Codex, Cursor and any coding agent.
Is it for engineers or leads?
Both. Engineers get the build order; leads get a way to assess their team's setup.
Is it free?
Yes. It is a free Lightning session on Maven, and signing up gets you the recording.
After this session
The Live Labs build one agent system piece by piece, free, with time for your questions. The buildcamp builds all of it with you over four weeks. Join a free Live Lab or see the buildcamp.