Skip to content

Processes/software — the spec, build, review, ship loopsoftware

Ship a feature (spec to deploy) — software processShip a feature (spec to deploy)

complexpartially automatable🔁 daily

The whole software-making loop: spec it, track it, implement with a coding agent, open the PR, pass AI and human review, deploy through CI, and verify in production.

Agents can draft the spec, cut the issue, implement, open the PR, and deploy through CI. Human code review and the merge decision gate the loop.

Current agent ceiling

An agent can run 7 of 8 steps 1 of them behind a human approval gate ⏸

Irreducibly human (1): Human review and approval (needs a human)

How it runs

Route-coded block flow: emerald = agent, amber = manual form/portal, red = needs a human. ⏸ approval gate · ⏳ async wait.

02Create the tracking issue

agent

or:Notion logoNotion59·monday.com logomonday.com52

1 API call
  • issueCreate

04Open the pull request

agent

or:GitLab logoGitLab54·Gitea logoGitea34

1 API call
  • POST /repos/{owner}/{repo}/pulls

06Human review and approval

human

07Merge and deploy via CI

agent
GitHub logoGitHub71⏸ approval gatemedium risk
1 API call
  • PUT /repos/{owner}/{repo}/pulls/{number}/merge

Context the agent needs first: feature requirements (from the founder)

The market options

Each role resolves against its arena’s live leaderboard — the default is the process’s canonical vendor, alternatives ranked by agent-readiness.

Simulate this process

simulated dry run from the mapped process — no real calls are made
For agents Process manifest (JSON)·/llms.txt