Skip to content

The Build Loop, Remote-Gated

Syntaxis core workflow with two proposed additions: plans round-trip through a pull or merge request on the team’s git host before /overview will read them, and /complete opens a request instead of merging locally

Everything in gold is the shipped Build Loop, completely unchanged — same numbered steps, same ring, same gate. The two dashed teal panels at the bottom are the only proposed additions, each fed by a dashed line from the exact point in the existing flow it attaches to.

Attaches to 03 · /overview itself, not to the arrow feeding into it — that placement matters. /overview doesn’t just read the plans; today it’s also where they first get committed at all, in its own existing Step 4 (“offer the initial planning baseline commit”), after Steps 1–3 already read them. /discovery never commits or pushes anything — Step 2 (Plan) is just files sitting on disk, however they were written.

So the gate is a new Step 0 inside /overview, not a change to /discovery or to how you approve plans in chat. When remote.planApproval is "remote-request", /overview’s first move is to check whether the on-disk plans are already reachable on the host’s protected default branch. If not, it commits just those files to a branch, pushes, opens a request, and stops — before Step 1 ever runs. Once that request lands, a re-run proceeds through Steps 1–4 exactly as today.

Nothing about /discovery, hand-writing plans, or /overview Steps 1–4 changes. The only new behavior is the one-time commit-and-possibly-stop in front of all of it.

Attaches to 07 · /complete. Today, /complete squash-merges the finished work straight into local main, then separately asks about pushing. Under this proposal, when remote.completeApproval is "remote-request", Steps 0–2 (safety pass, archive, one squash commit) run exactly as they do today — that archive already contains the findings and independent-review receipt a reviewer needs. Step 3 changes: instead of merging, it pushes the branch and opens a request with that archive in the body, then stops. A new follow-up, /complete resume, checks whether the host has since merged it — only then does local main fast-forward to match.

  • /onboard, /feature, /implement, /check, /check guide, and /audit — none of these are touched by this proposal.
  • The findings ledger and its P0/P1 block on completion — unchanged; it now blocks a request from opening instead of a local merge, but the rule itself doesn’t move.
  • Both new gates default to off. A project that never sets remote.* in syntaxis/config.json behaves identically to today.
Today Proposed
Plans land Committed by /overview’s Step 4, after it already read them /overview’s new Step 0 commits and opens a PR/MR before reading anything
/complete Step 3 Local squash-merge, then optional push Push + open request, stop; merge happens on the host
Getting to a merged main One command, one session /complete opens the request; /complete resume finishes once the host approves it

See Remote-Gated Approval for the full skill-by-skill design, the provider abstraction, and the open constraints.