plan-page
Plan page
The user reads pages, not replies; the block's Plan pages rule says when to publish and what the reply holds. A subject is one thing the work changes, and it has one page. Its file, <plans>/topics/<slug>.md, holds the current state. Each plan that continues it is an iteration carrying only its delta. node .agents/pstack/plan-page.mjs <plan> renders the page from both into <plans>/artifacts/, a local copy that regenerates from the committed plan and subject files, which are the record. node .agents/pstack/plan-page.mjs --index renders every subject's page there and an index linking them. A published claude.ai page is where the user comments on one hand-back; it is not the record. sync-pstack ships that renderer and status.mjs into every project it manages.
Read references/shape.md before writing a plan or a subject file. It holds every file shape, the page order and the renderer's refusals.
| Mode | Use it to |
|---|---|
| Render | publish a page at every stop the block's Plan pages rule lists |
| Refresh | render the named plan's page again with Render steps 5, 7 and 8 while the plan is not done; with no plan named, use the open plan of the subject the session works on, and ask when there is none |
| Check | audit a plan and its subject before handing the page back |
| Repair | fix a page whose shape is wrong |
| PR | write or update a PR body as the page of the PR's plan, or a comment about your commits on someone else's PR |
| Change | change the page shape, the renderer, or a playbook's page sections |