Preview and Resume
Preview
- Run Steps 1–7 with live reads, and make no writes. Never ask the user to install GitHub or change a setting in the browser; list those steps in the checklist.
- In Step 1, leave out the "Change one setting" option, because that hand-off writes.
- For release plans, use MCP reads only. For the flag release plan, read the list with
get-flag-release-planswhen the server has it. Without it, ask the user to run nothing, not even the list command (the release plans skill's own Read-only mode asks the user to run a read, but a preview here asks for nothing). List the plan to create in the checklist, and, without the tool, give its list and create commands as optional follow-ups. - In Step 7, show the plan as a checklist under "Changes an admin would make", one line per change, and stop without asking for confirmation. Leave out anything that needs no change, and add no other section (such as "Already set up").
Resume
- Keep the earlier mode: a resumed Preview stays Preview.
- Skip Step 0 entirely. Re-read live state in Step 1, and say in one sentence what is already done.
- Use the earlier picks if they are still in the conversation. If not, ask them again with live state as the default.
- Writes that landed before a Step 8 failure show as already set up, so the new plan lists only what is left.
- Browser steps that were still pending when the flow paused (bring your own key, turning on auto-archival) come after the confirmation again: list them in the new plan and walk through them in Step 8.
- A restated pick is an answer, never approval. Resume still stops at Step 7 and waits for "Looks good".
Every mode is safe to run again: a re-run reads live state and proposes only the writes that are still needed.