From dd86279e88e4bbe1bd67f475673f506410a0b1b5 Mon Sep 17 00:00:00 2001 From: Justin Parker Date: Sun, 8 Nov 2026 23:14:09 -0800 Subject: [PATCH] Ask for sign-off after Quick Task's See it running demo AI Assisted --- src/plan2code-quick-task.md | 2 +- src/web-console/notes/implement.md | 2 +- src/web-console/notes/quick-task.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/plan2code-quick-task.md b/src/plan2code-quick-task.md index c5da48c..463d810 100644 --- a/src/plan2code-quick-task.md +++ b/src/plan2code-quick-task.md @@ -161,6 +161,6 @@ Ready to implement? (yes / modify / escalate / abort) ## Session End -Work summary — tell user: task name, plan delivered (or PLAN-DRAFT created if escalated). After a build, offer: "Reply `show me` to see it running." A review the person asks for after the build runs as `references/review-in-build.md` says. **Show me it working** (offered, never required): start the app as `AGENTS.md` Commands says (missing: work it out from `package.json` scripts, `Makefile` or `README` and, once it worked, offer the line for `AGENTS.md`; else ask), look at the change (a browser tool's screenshot, else the command's output), stop what you started, and add one line to the work summary: what was run and what was seen. Screenshots go on the web console page only. +Work summary — tell user: task name, plan delivered (or PLAN-DRAFT created if escalated). After a build, offer: "Reply `show me` to see it running." A review the person asks for after the build runs as `references/review-in-build.md` says. **Show me it working** (offered, never required): start the app as `AGENTS.md` Commands says (missing: work it out from `package.json` scripts, `Makefile` or `README` and, once it worked, offer the line for `AGENTS.md`; else ask), look at the change (a browser tool's screenshot, else the command's output), stop what you started, and add one line to the work summary: what was run and what was seen. After the demo, ask "Looks right, or want changes?" and make any change before the summary. Screenshots go on the web console page only. **On the web console:** after a build, keep waiting for the review button's answer before you stop. diff --git a/src/web-console/notes/implement.md b/src/web-console/notes/implement.md index 7513b60..f6be225 100644 --- a/src/web-console/notes/implement.md +++ b/src/web-console/notes/implement.md @@ -34,7 +34,7 @@ A later phase in the same session asks with a new id (`signoff-phase-2`, title " ### Show me it working -On `show`, run the workflow's **Show me it working** paragraph. Save screenshots under the session's `shots/`, never `specs/`, and post them as image blocks in a `shown` doc with what was run in a `md` block above (no browser tool: that block alone says what the command printed). Then reopen the same card without the `show` verdict, with a `thread` reply naming what was seen. Same on Finalize's card and the one `building-review.md` reopens; Quick Task's card is settled instead. +On `show`, run the workflow's **Show me it working** paragraph. Save screenshots under the session's `shots/`, never `specs/`, and post them as image blocks in a `shown` doc with what was run in a `md` block above (no browser tool: that block alone says what the command printed). Then reopen the same card without the `show` verdict, with a `thread` reply naming what was seen. Same on Finalize's card and the one `building-review.md` reopens; Quick Task's card is settled instead, and a "Does it look right?" card follows it (`notes/quick-task.md`). ## After approval: the finish diff --git a/src/web-console/notes/quick-task.md b/src/web-console/notes/quick-task.md index b641379..fdf20ab 100644 --- a/src/web-console/notes/quick-task.md +++ b/src/web-console/notes/quick-task.md @@ -26,7 +26,7 @@ Read `building.md` first. ``` A step that cannot be done is `- [!]` with the reason, not counted in `cleared`. A step added mid-build raises `headline.total` in the same post. Tick Verify boxes in the post that reports the checks. Do not `wait` until the build is done. -- **See it running, before the finish:** once built, post `review` "See it running" (`"doc":"plan"`, verdicts `show` ("Show me it working"), `fine` ("No need, finish up"), tokens `show me` / `no`) with `--wait`. On `show`, see `notes/implement.md` → Show me it working; its one line goes in the finish `body`. Settle the card in the finish post. +- **See it running, before the finish:** once built, post `review` "See it running" (`"doc":"plan"`, verdicts `show` ("Show me it working"), `fine` ("No need, finish up"), tokens `show me` / `no`) with `--wait`. On `show`, see `notes/implement.md` → Show me it working; its one line goes in the finish `body`. `fine` settles the card in the finish post. After `show`, settle it in the post that shows it, then post `review` "Does it look right?" (`"doc":"shown"`, verdicts `fine` ("Looks right, finish up"), `changes` ("I want changes"), tokens `approved` / `needs changes`) with `--wait`. `changes`: make it, reshow if visible, reopen with a `thread` reply, wait again. Only `fine` leads to the finish. - **Archive a fixed bug:** launched on a diagnosed folder and now Fixed with nothing past the diagnosis, post `confirm` "Archive this bug?" in the same post as "See it running": dry run's `files` in `body`, `yesLabel` "Archive it", `noLabel` "Keep it in specs/", `consequences` naming `specs--completed//`. Yes: `node "/specs.mjs" archive `, and say where it went in the finish `body`. - **Finish after the build:** `command` is the filled-in commit command in the project's format (AGENTS.md), `"where":"When you are happy with it, commit it from your terminal:"`, with `review` (**Review it now**), `"commit":true`, `"changelog":true` and `"dashboard":true`. Review and dashboard are required. Whichever button is pressed, what follows is `building-review.md`. - **Escalated / aborted:** settle the verdict in the finish post: `"command":"/plan2code-1-plan"` with the PLAN-DRAFT's path in `body`, no review; or `"command":"/plan2code-quick-task"`. Both `"dashboard":true`.