From 36648c3e75ed46a86bfc7b185b37bc113b7c047f Mon Sep 17 00:00:00 2001 From: Justin Parker Date: Thu, 12 Nov 2026 11:21:51 -0800 Subject: [PATCH] Offer to archive a prototype-only spec folder once Quick Task has built from it AI Assisted --- .readme/web-console.md | 3 ++- scripts/test-console-wire-budgets.mjs | 2 +- src/plan2code-quick-task.md | 2 +- src/plan2code.md | 2 +- src/web-console/notes/quick-task.md | 2 +- 5 files changed, 6 insertions(+), 5 deletions(-) diff --git a/.readme/web-console.md b/.readme/web-console.md index 481990a..44f2db0 100644 --- a/.readme/web-console.md +++ b/.readme/web-console.md @@ -142,7 +142,8 @@ Scroll down for the utilities. Outside a git repository the **Git** card says so picked on the dashboard, or the session's own) has saved UI prototypes in its `prototypes/` folder, a **Prototypes** tab lists them. An `.md` opens in place, with **Back to Prototypes**; an `.html` opens in your default - browser. + browser. Once Quick Task has built from a folder that holds only + prototypes, it offers to archive that folder to `specs--completed/`. - **Where you are, at the bottom.** The footer names the folder the session was launched from and its git branch (`plan2code · feature/…`), muted in the middle. Click it to open the Workspace dialog (see *Your workspace*). diff --git a/scripts/test-console-wire-budgets.mjs b/scripts/test-console-wire-budgets.mjs index 404b172..28d097f 100644 --- a/scripts/test-console-wire-budgets.mjs +++ b/scripts/test-console-wire-budgets.mjs @@ -41,7 +41,7 @@ export const BUDGETS = { "pathfinder.md": 2622, // raised by the UI prototype line's bytes only "plan.md": 1023, // raised by the UI prototype line's bytes only "pr-prep.md": 4500, - "quick-task.md": 4589, // raised by the UI prototype line's and the prototype recap line's bytes only + "quick-task.md": 4729, // raised by the UI prototype line's, the prototype recap line's and the prototype archive wording's bytes only "review.md": 1000, "revise-plan.md": 1422, // raised by the UI prototype line's bytes only "test.md": 5400, diff --git a/src/plan2code-quick-task.md b/src/plan2code-quick-task.md index 46954b2..1ab2e54 100644 --- a/src/plan2code-quick-task.md +++ b/src/plan2code-quick-task.md @@ -39,7 +39,7 @@ Check for `./AGENTS.md` first: - Complete clarification before presenting the plan; keep it concise, actionable and about this change only - Standalone workflow - does NOT create spec files or feed into steps 2-4 - Launched with a spec folder holding a `DIAGNOSIS-*.md`: read it first, as the bug's context (its cause and suggested fix are already found; re-run its reproduction before and after the fix). Once it passes, set the diagnosis `**Status:**` to `Fixed`; escalating, use that folder rather than asking for a name. Fixed, with nothing in the folder past the diagnosis (no `PLAN-CONVERSATION`, `PLAN-DRAFT`, `pathfinder/map.md` or `overview.md`)? It is done: run `node "/specs.mjs" archive --dry-run` from the project root (`` is `scripts/` beside this SKILL.md, `~/.agents/skills/plan2code-quick-task/scripts/` globally), show its `files`, ask "Archive it to `specs--completed/`? (yes / no)", and on yes run it without `--dry-run`. On no it stays on the dashboard as "Bug fixed". -- Launched with a spec folder holding only saved prototypes (`prototypes/.html` and `.md`): read each `.md` first, as the brief (the request, the chosen variant and its settings, why the others lost), and open the `.html` for the look; with several, ask which to build. Then show what you read (the request, the chosen variant and the settings carried over) and ask them to confirm or add to it before any follow-ups or plan; this stands in for asking what to build (console: a `recap` card). Build the chosen variant into the app's own code and styles, never the prototype page itself, and skip the "See it first?" offer. Escalating, use that folder rather than asking for a name. Nothing is archived: the prototype stays as the reference. +- Launched with a spec folder holding only saved prototypes (`prototypes/.html` and `.md`): read each `.md` first, as the brief (the request, the chosen variant and its settings, why the others lost), and open the `.html` for the look; with several, ask which to build. Then show what you read (the request, the chosen variant and the settings carried over) and ask them to confirm or add to it before any follow-ups or plan; this stands in for asking what to build (console: a `recap` card). Build the chosen variant into the app's own code and styles, never the prototype page itself, and skip the "See it first?" offer. Escalating, use that folder rather than asking for a name. Built, with the folder still holding nothing but `prototypes/`? Offer to archive it as for a fixed bug (dry run, its `files`, "Archive it to `specs--completed/`? (yes / no)"), naming any prototype not built; on no it stays on the dashboard as "Files on disk". - Cause unclear or the fix big? Stop and suggest `/plan2code-diagnose`. - Read `references/building-habits.md` when the ask is a bug fix or a test fails unexpectedly, after a yes to "Write the test first?", and before a change meant to alter no behavior; follow it. - Read `references/test-runs.md` before the first test run: run the tests covering the changed files, and offer the full suite at sign-off when the change touched shared ground. diff --git a/src/plan2code.md b/src/plan2code.md index d6ea91d..8f3a454 100644 --- a/src/plan2code.md +++ b/src/plan2code.md @@ -57,7 +57,7 @@ Ground truth for menu notes and Ask-tab answers. For anything beyond this table, | 0-pathfinder | the idea, loose notes | `pathfinder/map.md`, `pathfinder/questions/NN-.md`; cleared → `PLAN-DRAFT-.md`; a UI prototype's `prototypes/.html` and `.md` on a yes | | 1-plan | idea or `PLAN-DRAFT` | `PLAN-DRAFT-.md`, `PLAN-CONVERSATION-.md`; a UI prototype's `prototypes/.html` and `.md` on a yes | | 1b-revise-plan | `overview.md`, `phase-X.md`, a waiting `**Plan change:**` brief | the same, revised; the brief marked applied or dropped; a UI prototype's `prototypes/.html` and `.md` on a yes | -| quick-task | the ask; a `DIAGNOSIS-*.md` when launched on one; a saved prototype's `.md` and `.html` when launched on its folder | code; the diagnosis set to `Fixed`, then the folder moved to `specs--completed/` on a yes; escalated → `PLAN-DRAFT-.md`; a UI prototype's `prototypes/.html` and `.md` only when asked | +| quick-task | the ask; a `DIAGNOSIS-*.md` when launched on one; a saved prototype's `.md` and `.html` when launched on its folder | code; the diagnosis set to `Fixed`, then the folder moved to `specs--completed/` on a yes; a built prototype's folder moved there too on a yes; escalated → `PLAN-DRAFT-.md`; a UI prototype's `prototypes/.html` and `.md` only when asked | | 2-document | `PLAN-DRAFT`, `PLAN-CONVERSATION` (optional) | `overview.md`, `phase-X.md` | | 3-implement(-review) | `overview.md`, `phase-X.md` | code; `[x]` marks + completion summary in `phase-X.md`; paused for a revision, a `**Plan change:**` brief in its Notes | | review | spec, diff | the fixes picked; no spec writes | diff --git a/src/web-console/notes/quick-task.md b/src/web-console/notes/quick-task.md index 6a27abb..0c45674 100644 --- a/src/web-console/notes/quick-task.md +++ b/src/web-console/notes/quick-task.md @@ -29,7 +29,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`. `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`. +- **Archive a fixed bug or a built prototype:** launched on a diagnosed folder and now Fixed with nothing past the diagnosis, or on a folder of only prototypes now built, post `confirm` "Archive this bug?" (or "Archive this prototype?") in the same post as "See it running": dry run's `files` in `body`, with any prototype not built named there, `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`.