Live sessions for engineering teams and the leaders who set their rules, run on your repo instead of a demo app. Each session leaves a file behind, so your team goes from trying Claude Code to shipping with it daily.
The founder runs every session: a former Head of Software Engineering with 14 years building production software.
Acme Inc training planNotes in your repo
Claude for leaders
Claude Code team workshop
rules/agents.mdCLAUDE.md.claude/skills/spec/SKILL.mddocs/decisions/.claude/skills/review/SKILL.mdrules/parallel-work.mdacme-app
Claude for leaders
Heads of engineering and product, and the leads who will own the rules.
rules/agents.mdadded to your repo
Claude Code team workshop
Every engineer on the team, with your repo open.
CLAUDE.mdadded to your repo
Claude Code team workshop
Engineers and the product manager who writes the tickets.
.claude/skills/spec/SKILL.mdadded to your repo
Claude Code team workshop
Engineers, and whoever knows why the code looks the way it does.
docs/decisions/added to your repo
Claude Code team workshop
Engineers and the people who approve pull requests.
.claude/skills/review/SKILL.mdadded to your repo
Claude Code team workshop
Engineers already running more than one agent.
rules/parallel-work.mdadded to your repo
Most teams have had the tutorial. Engineers still ask Claude Code one question at a time and paste the answer. Three reasons come up on almost every call.
It was taught on someone else’s code. A demo app has no history, no odd module, no payments code nobody wants to touch. The first real ticket looks nothing like the exercise.
Every engineer set it up alone. One person’s instructions live on one laptop. The next engineer starts from nothing, and the agent behaves differently for each of them.
Nobody wrote down the rules. What may an agent change on its own? Who reviews it? Until a leader answers that, careful engineers stop short and the rest guess.
We run the sessions on your repo with your leaders and your team. Every session ends in a commit, so the setup and the rules live where the next engineer looks first.
Every engineer starts from the same setup.
Instructions, permissions and the shared commands live in the repo, so the agent behaves the same for each person.
Tickets become specs before the agent starts.
The team writes the goal, the checks that prove it and what is out of scope, with a spec skill it runs on the next ticket.
Reviewers read for intent.
A review skill and a definition of done clear the mechanical comments on every pull request.
Leaders answer what agents may touch.
The rules are written down once, with an owner, and the teams work from them.
Files in your repo that the next engineer, and the next agent, read first. Open any of them.
acme-appnew
.claude/
skills/
spec/
review/
checks/
docs/decisions/
rules/
CLAUDE.mdOne shared setup.claude/settings.jsonOne shared setup.claude/skills/spec/SKILL.mdSpecs before code.claude/skills/review/SKILL.mdReview that keeps upchecks/definition-of-done.mdReview that keeps updocs/decisions/0001-payments.mdContext agents can readrules/agents.mdClaude for leadersrules/parallel-work.mdAgents that stay out of each other’s wayEvery session ends in a commit,
so the habit stays in your repo after we leave.
Leaders decide what agents may touch. Then the team builds the setup that follows those decisions. Pick any session in the training plan to see what it covers.
We read it before the sessions, so the exercises use your code from the first minute.
For heads of engineering and product and the leads who will own the rules. It turns “should we let agents do this?” into a written answer your teams can work from.
For the whole team, on your repo. Each block takes one habit (shared setup, specs, context, review, parallel work) and ends with the file that keeps it in place. Every file the sessions write is committed to your repo.
“You work with the person who does the work. No handoff, no juniors, no account manager.”
Paramanantham HarrisonFounder, KaaS.team
Yes. The Claude Code team workshop runs on your own repo with the whole team in the room. Claude for leaders runs alongside it for the people who own the rules.
Teams whose engineers already have Claude Code and each use it differently. You want the sessions run on your own code, and someone on your side will own the rules once the sessions end.
Teams who want a recorded course to watch later, or prompt tips more than a shared setup. It also needs someone with time to commit the files the sessions write.
The founder runs every session. No juniors, no handoff to a trainer you have not met.
Both. Remote sessions run live on a call with everyone in your repo. Onsite sessions run in your office.
We work in the repo you pick, with the access you give. Before the sessions we read it so the exercises use your code, and every file the sessions write is committed to your repo.
Yes. Leaders only runs Claude for leaders on its own, and the rules it drafts go to your teams. One team adds the Claude Code team workshop on that team’s repo. Several teams start with leaders, so the rules exist, then one workshop per team.
Training teaches the team and leaves the first files. A Claude Code rollout installs the shared setup across one or more teams and reports where it landed.
Training gets the first files into the repo. A Claude Code rollout installs the shared setup across one team in 14 days, or a department or the whole engineering org in 60 or 90. The Software Factory Buildcamp is for the lead who will run it after us.
No. Claude for leaders is about decisions: what agents may touch, who reviews what, how you will know it worked. The rules it drafts are written in plain language.
Fit check first. If we're not the right team, we'll say so on the call.
You get a written scope and a fixed quote before anything starts.
Every file the sessions write is committed to your repo and stays there.
A 30 minute call with the founder about where work is stuck.
We find where the work waits and whether we can help.
You get a written scope and a fixed quote before anything starts.
Work starts with your product and engineering leads.
If we're not the right fit, we'll say so.
Open the calendar and choose any free slot. You get an invite with a video link.