Agent SDLC
Software delivery, operated by an agent. Governed by your engineers.
Assign a project the way you would assign a lead engineer. The agent designs it, breaks it into tickets, builds it in an isolated sandbox, reviews its own pull request, and stops at two gates your engineers hold.
The problem
The expensive part was never the typing.
It is the queue, the coordination, the context switching and the calendar. A feature a customer describes in a paragraph still waits weeks for a team to pick it up, plan it and ship it.
The lifecycle
From a ticket to a merged pull request. Your effort: two approvals.
Assign it
Pick a project or a single issue in Linear or Manifest Projects, and name the PM who answers its questions.
It studies and designs
A read-only study of your real repository returns an approach, the files involved, the risks, and a breakdown into buildable tickets.
It asks instead of guessing
Material unknowns go to the PM as written questions, and the delivery pauses until they are answered.
Design approval
A gatekeeper approves, asks for changes or rejects, in Slack or the console. Nothing is built before this.
Ticket by ticket
A Claude Code builder works in an isolated cloud sandbox on a preview branch. Tickets move across your board as it goes.
It reviews its own work
One pull request, an inline review for completeness, practice and security, every CI check quoted verbatim, and the running cost.
Merge approval
Never skipped. CI is re-read on the exact commit at merge time. Change requests loop back as corrective builds.
Ready for QA
Tickets move to QA, and the PM gets a summary with the pull request and the preview link.
Governance
The gates are yours to loosen, never ours.
Named gatekeepers
Every decision records who, when, from where, and with what comment.
Honest about CI
Claims cite CI, checks are quoted verbatim, and a running check counts as not passing.
Bounded autonomy
One corrective attempt, then it escalates with evidence. A watchdog wakes stalled deliveries.
No production keys
Builds run in single-tenant sandboxes with one-hour GitHub credentials. Your pipelines deploy, not the agent.
Fits your stack
Works in the tools you already use.
Your tracker, your repositories, your CI and deploy pipelines stay as they are. The model runs on your own account.
Assign from your board, or use our built-in tracker
A scoped GitHub App, short-lived credentials
One live status message and one decision thread per delivery
Your Anthropic key or Claude Code subscription
Not a coding assistant
It owns the delivery, not the keystrokes.
Getting started
An implementation engagement, together.
GitHub, your tracker, Slack, your model key
Gatekeepers, budgets, repositories, CI
First projects, side by side with us
More projects in parallel, gates loosened by you
Pricing
Priced for your team.Every team starts with an implementation engagement. Tell us about your repositories and how you deliver today, and we will put a price on it.
Talk to us →We run it on ourselves
Every new project at Manifest ships through Agent SDLC, with our engineers holding the gates.Pairs with Agent SRE
Agent SRE files the fix-ready ticket. Assign it here and the fix ships through the same gates. Explore Agent SRE →Hand us a project. Keep the gates.
We will connect your stack, run your first deliveries with you, and leave you in control.