Skip to content

The Adopt Loop, Remote-Gated

Syntaxis existing-codebase workflow with two proposed additions: the surveyed plan round-trips through a pull or merge request before /overview will read it, and /complete opens a request instead of merging locally

Everything in gold is the shipped Existing Codebase workflow, completely unchanged — including the dashed /fix · /debug alternate entry into the ring. The two proposed panels attach at the same two points as the fresh-project Build Loop, because /adopt feeds the ring through the exact same two commands, /overview and /complete.

Attaches to 02 · /overview itself, not to /adopt. /adopt only writes project-plan.md / build-plan.md to disk, the same as a hand-written plan — it doesn’t commit or push anything. The one real difference from a fresh project is what /overview finds on disk: /adopt’s inferred plan, surveyed from what the application actually does, with shipped features already checked off, instead of something you typed. Under this proposal it gets exactly the same treatment as any other plan source: /overview’s new Step 0 commits it to a branch, opens a request on the git host, and stops before Step 1 reads anything. A brownfield project’s plan doesn’t get a lighter review just because a machine wrote the first draft.

Attaches to 06 · /complete, identically to the fresh-project diagram, and for the same reason: a change that entered the ring through /feature and a change that entered through /fix · /debug are archived, committed, and completed identically once they reach this node — so the remote gate applies the same way regardless of which door the work came in through.

  • /adopt’s survey behavior, /feature, /fix, /debug, /implement, /check, and /audit — none of these change.
  • The dashed /fix · /debug alternate entry and everything about how it merges into the ring at node 03 — unchanged.
  • A brownfield project’s /audit baseline and QA backfill process — both described in Existing Codebase — are unaffected.
Today Proposed
/adopt’s surveyed plan Committed by /overview’s Step 4, after it already read it /overview’s new Step 0 commits and opens a PR/MR first, same as a hand-written plan
/complete, from either entry point Local squash-merge, then optional push Push + open request, stop; /complete resume lands it once approved

See Remote-Gated Approval for the full skill-by-skill design, and The Build Loop for the equivalent fresh-project diagram this one mirrors.