Specs
Spec Branches
A Spec is the parent Issue for a Medium or Large Intake Session. Enable Spec Branch during plan review to integrate its sub-issues on spec/<N>-<slug> before one Spec Pull Request carries the work to the Base Branch. Sub-issue Pull Requests target the Spec Branch. The Dashboard'sSpec Group shows their progress and the final Landing state.
Choose the branch route before publishing
The Spec Branch choice and target are fixed at publication. Branch setup must succeed before sub-issue Dispatch or Spec Refresh can proceed.
Auto-land authorizes automatic Spec Landing. With it off, review the Spec Pull Request and choose Land Spec when ready. Both paths wait for all children to close with at least one completed child. See Watch a Project for branch and Auto-land controls.
Spec Refresh and Pull Request Repair
A Spec Refresh merges the Base Branch into an open Spec Branch, keeping its integrated work current. The Landing Queue serializes each Spec Refresh with sub-issue Landings. In-flight Runs continue and catch up at their own Landing.
Zozo queues a Spec Refresh after a Landing onto the same Base Branch. Once every sub-issue is closed and at least one completed, Zozo performs one final Spec Refresh before opening the Spec Pull Request for review or automatic Landing. The merge preserves history and is pushed without a separate verification Pull Request. The next sub-issue Pull Request and the final Spec Landing verify the integrated result.
Spec progress shows the Landing Phase and Landing Block Reason. Refreshing means the branch is catching up. Choose Refresh now after you move the Base Branch outside Zozo. It's unavailable for a Spec closed as not planned, a paused Project, a landing-blocked Spec, or before Spec Branch setup succeeds.
A conflicting Spec Refresh gets a bounded Landing Repair Run on the Spec's repair Thread. If repair can't resolve it, refresh-unresolved blocks further refreshes and appears on Needs Attention. Sub-issue Dispatch and Landings continue. Inspect and fix the branch, then choose Retry refresh to clear the reason and landing-blocked label and enqueue another Spec Refresh. Starting a refresh doesn't notify you.
The Spec Pull Request also receives conflict and failing-check repair under the usual repair limits and Project stop conditions. Repairs reuse the Spec's repair Thread, with the Spec body, sub-issue Pull Requests, and intervening Base Branch commits as context. Resume a paused repair Thread before repair can proceed. Automatic and manual Landings use the same repair rules.