Agentic software development on Claude CodeSix agents. One pipeline.
A person at every gate.
This is the delivery pipeline every Hopsig build runs on. Each stage is an agent with a defined input, output and guardrail; each handoff can be stopped by a person. Run a story; the detail is below.
6
stages, each an agent with a defined input, output and guardrail
3
points where a person signs: the plan, the pull request, any escalation
0
merges to main by an agent
1
pipeline for every Hopsig build, and the one we install on yours
What they never do.
Written into the guardrails · press one
Merge to main
Change the guardrails, the CI or the branch rules
Touch a production environment or production data
Decide scope, or add to it
Sign off an increment
Spend money, open accounts or talk to your users
Carry on when a person has said stop
The flow.
Agents outlined · a person in Lime
StageInOutGuardrailWho decides
01
Plan
Solutions-architect agent
InA brief in plain language, the repo, your conventions
OutA plan: components, risks, the order of work
GuardrailNothing is built from a plan a person has not read
A person signsYou read the plan and object before any code exists.
02
Stories
Story agent
InThe approved plan
OutEpics and stories in your Jira or ours, with acceptance criteria
GuardrailEvery story traces to a line in the plan
No gateRuns on its own inside the guardrail
03
Build
Implementation agent
InOne story, your codebase, your guardrails
OutA branch with the change, inside your conventions
GuardrailLint, CI, branch rules and review policy, enforced on every change
No gateRuns on its own inside the guardrail
04
Review
Review and test agents
InThe branch
OutA reviewed diff with generated tests, and a pull request
GuardrailA senior always looks before it merges
A person signsA senior engineer reviews the pull request. Agents never merge to main.
05
Document
Docs agent
InThe merged change
OutDocumentation updated as the code changed
GuardrailDocs live with the code, never a handover task
No gateRuns on its own inside the guardrail
06
Escalate
Escalation agent
InAny decision outside the guardrails
OutA question pushed to a phone, with the context, while the pipeline waits
GuardrailNo guess where a person should decide
A person signsA person answers; the pipeline resumes or stops.
Agentic flow · the call
See it run on one of your stories.
Bring the problem, not a brief. If it is outside what we do well, we will say which of our contacts to call instead.
Or email info@hopsig.com — reply within one working day.