# Plan pages This file says how a plan becomes a page, what the page and the hand-back reply hold, and how calls become Defaults or Open questions. The pstack block in `AGENTS.md` points here. The `sync-pstack` skill renders this file from its shared source in `udecode/dotai`, so change it there. - **Plan pages.** In Claude Code, every subject has one page, and every plan that continues it is an iteration on that page, never a page of its own. A plan takes the shape the `plan-page` skill describes, instead of the PR sections Multi-phase plan's step 3 lists. Load the `plan-page` skill before writing or changing a plan, a subject file in `docs/plans/topics/` or its page. It owns their file shapes, picking the subject, the delta and the fold, `node .agents/pstack/plan-page.mjs` and its refusals, publishing, and changes to the page shape; each project playbook names the review sections its plans write. The committed plan and subject files are the durable record, and the rendered page under the plans directory regenerates from them; a project's index of every subject stays local, and the published page is where the user comments on one hand-back. An agent reads a page from its rendered file or from its plan and subject files, never from the published page, because another account may own that page. The one exception is the read of `index.html` by path that a refused publish's `--base` needs. Only `page-stop.mjs` starts from the published page, and it takes only the page file's list of runs from it. Only a page whose work is still active is published again, apart from the close stop's publish after the last land. Codex sessions render the page, copy the printed file into the run directory, and reply with that copy's path and the plan it renders. Any later render on the subject, `--index` included, rewrites the printed file. When the user returns, the lead renders that plan again and publishes the page. For a call the owner would notice, other than one the Autopilot rule stops on, pick the recommended option, record it as a row of the plan's `## Defaults` table (the decision, the pick, the alternative, the word that reverses the pick and its impact, as the `plan-page` skill says), and keep going. An option that leaves the user's stated goal unmet is never a default, and research that overturns the premise of a question the user answered reopens it. Before asking the owner, or running `architect`, about how to build an integration, the lead checks what each product already ships for the job in its own docs and settings, and searches for prior art. An interview the owner asks for covers only outcomes the owner alone can judge, such as what the owner sees, which cost is acceptable and what counts as done. Only a call the Autopilot rule stops on, or a message that waits as a draft as the Messages rule says, goes under `## Open questions` and to the user through `AskUserQuestion` where the runtime allows it, otherwise in the reply, recommended option first; the page shows it under Needs you as a decision memo the user answers in their own words. "go" takes the recommended option of each question shown except a production deploy or release, which takes the user's own answer to that question, typed or picked in `AskUserQuestion`, because the Delivery rule asks for an explicit request; an answer in the user's own words picks exactly what it says, and neither authorizes anything else. An answered question leaves Open questions, as a Defaults row or a decision-log row that quotes the owner's answer verbatim when it arrives. The user reads pages, not replies, so every stop that hands back work with a plan publishes its page before the reply, or in Codex renders and copies it as above, at whichever of these the run hands back: a plan written, back from review, revised or built, a review verdict other than a review-only panel's, a "next" answer, a playbook's close, a blocked run's ask, reflect's list awaiting approval and a subject file update. Between those stops the lead publishes only when it adds or changes an item under Needs you or a Defaults row whose Pick cell ends with (look) or (answer), and `stage` prints nothing to send for any other change unless the page has not shown this run's last publish, such as after a refused one. It publishes before further work depends on that choice and does not wait for a reply. In Claude Code every publish goes through `node .agents/pstack/page-stop.mjs`: `stage ` between stops and `stop ` at a stop. The helper writes the page file, which lists every run, and this run's header and body under the plans directory's `artifacts/pages//`, then prints the publish to send and every file in it. In the next message the lead reads each named file in full, in ranges when one read cannot hold it, and views each named picture. The printed publish then goes out with the next working call. A long call starts in the background, so a publish never waits behind it. The lead never sends a publish the helper did not print or the whole page the renderer prints. When the Artifact tool refuses the publish and returns the page's live version, such as when the session has not viewed it or the page changed, the lead runs the same command again with `--base ` and sends what it prints; when no file was saved, it reads the page's `index.html` by path first and passes that file. A subagent never publishes a page. A publish sends only the page file and this run's own files, so every other run's files stay. When the page does not open, because it was deleted or another account owns it, the lead runs the command again with `--new` without asking the owner, and follows the `plan-page` skill's Render step for a link that no longer opens. Between stops the page's stage line shows the stage of its last publish, and an old helper's whole-page publish hides other runs until that worktree rebases onto these helpers. Where a Claude Code session publishes between stops, a Codex session instead renders the page, copies the printed file into the run directory and names that copy's path in a progress message, then keeps working. Otherwise the lead renders the page only to check its own change. Topic work renders the plan the stop is for, which leads its subject's page, and publishes to that page; a review verdict or a "next" answer with no subject writes a one-off plan and publishes that. Work that keeps no plan hands back in its reply instead, as the Plans and trails rule says. The block's Plan pages rule says when `stage` runs. The plan's `## Close` holds what a close used to report: what landed, the proof and its limits, reversals first, and open work with owners and stops; a pstack playbook's Reply line lists what else its Close holds. The reply that hands back work with a plan names what landed in a sentence and ends with its link list: the link `stop` prints once its publish went through, 📄 and the page URL plus `#run-`, which lands on that plan's part of the page even after another run publishes, then the link of each commit the session landed for the request, as land.md's Review rule counts them. In Codex, the path of the page's copy takes the page link's place. Any reply or report places and formats its page and commit links as writing.md's Links in replies rule says. After a review-only panel the findings also go in the reply, and a direct question from the owner gets its plain answer before the link. When the user's reply language differs from the page's, the hand-back reply gives the Brief in the user's language next to the link. A direct question or a one-file edit answered in the conversation stays in chat, but an answer that discloses something about a topic's work, such as a skipped gate or a design limit, also goes on that topic's page. Leave out an empty part instead of announcing it. A Closing summary, in a reply long enough for writing.md to ask for one, still opens by naming what waits on the owner or saying that nothing does.