▲ For your CTO · method v2026.09

The technical detail.
How it works inside.

The method is a versioned document. Here is every stage with its artifacts, every human gate and what changed in each version.

01 · Stages

stage 01
Requirement
An agent turns the need into a spec against the real code. Specs live in the repo and tell the agent how to decide.
specs/*.md▲ Product approves
stage 02
Build
Agents in parallel worktrees implement, test and document. Each task runs isolated with its own agent.
worktree/* · tests
stage 03
PR gate
Automated review of quality, security and business rules. Risk is classified before asking for human review.
pr/review · risk score▲ Human review
stage 04
Release
Deploy to production with specs updated in the same PR that changed the code.
release/2026.09.x▲ QA approves
stage ∞
Continuous operation
Operations agents diagnose every production error, propose the root cause and open the ticket (stage 01) or the fix PR (stage 03).
error → ticket · error → PR

02 · Human gates

Review is proportional to risk. Not everything goes through a person.

▲ Product
Before building
Product validates the spec: what gets built and why. It's the cheapest decision to correct.
▲ Review
On the PR, by risk
Low-impact changes merge with agent review. High-risk ones are reviewed by a person.
▲ QA
Before release
A person validates behavior before it reaches your users.

03 · Changelog

Sep 27, 2026current

Four stages, three gates. Operations feed back into the flow.

NewThe PR gate classifies risk before asking for review. Low-impact changes merge with agent review.
NewOperations agents open the fix PR, not just the ticket.
ChangedSpecs are updated in the same PR that changes the code.
RemovedPer-team prompt templates. Context lives in the repo.