Agent workflow

You decide. Agents plan, build and check each other.

Every change flows through the same loop, recorded in your PageSpace drive. You stop at two places: approving the plan and merging.

Plan→Plan review→Your approval→Board→Build→Independent review→Merge→Done

1 · Plan an epic

Ask your coding agent for an epic with the /task skill. It writes Plan — <Epic> in the drive's Plans folder: why, design, constraints, and a Manifest of leaves. A leaf is one pull request with criteria written as Given X, should Y, one assertion each. The Manifest's dependencies derive the timeline: stages, what can run in parallel, the critical path.

2 · Independent plan review

bun plan:review <planPageId>                       # reviewer from project.config.json
bun plan:review <planPageId> --runner claude
bun plan:review <planPageId> --runner codex --model gpt-5.5
bun plan:review --plan-file plan.md --runner opencode   # offline

A read-only reviewer (Codex, Claude Code or OpenCode) checks scope, leaf sizing, testable criteria, missing prerequisites, shared-file conflicts and the derived timeline. Changes requested means revise and review again; the review is published to the drive's Reviews folder.

3 · Your approval

The one stop. The plan link, the review verdict, the timeline and every open decision arrive in your drive's Epic Updates channel. Decisions an agent made on your behalf are recorded with bun decision:record in Pending decisions until you confirm or overrule them.

4 · The board

The epic, its phases and its leaves are created on the Roadmap, each leaf carrying its criteria verbatim and its prerequisites. Leaves move Ready → In progress → In review → Merged → Done. Only leaves whose prerequisites are Done become Ready.

5 · Build

Each Ready leaf gets a prompt page and a builder agent in its own git worktree with its own database slot. Builders work test-first, prove each criterion RED then GREEN, add negative controls, run bun check and the integration suite, open the pull request with /pr and hand off with /handoff.

6 · Independent review

A different agent reviews with /review: it re-runs every gate itself at the exact commit, runs its own negative controls, checks security and privacy, and publishes a review record naming the commit, the builder and the reviewer. Every finding outside the leaf is filed, never left in prose.

Reviews catch real things. In the first epic built this way, reviewers found two security gates that no test would have noticed being loosened, and a missing accessibility scan; each became a follow-up leaf.

7 · Merge

The review-record GitHub App sets the review-record status only when an independent record approves the pull request's exact head commit, and main requires it with CI and the browser tests. When you merge, a workflow moves the delivered tasks to Merged and posts to Sprint Room; Done comes only from the review.

Who does what

Role	Does	Never
You	Approve plans, decide scope, merge	Act as the message bus
Orchestrator	Plans, tasks, writes prompts, spawns agents, keeps the delivery log	Edits a delegated leaf's criteria
Builder	One leaf, one pull request, proven criteria	Reviews its own work or merges
Reviewer	Independent verification and the review record	Changes code or marks Done unasked

Command reference