Offer to archive a prototype-only spec folder once Quick Task has built from it

AI Assisted
This commit is contained in:
jparkerweb committed 2026-11-12 11:21:51 -08:00
1 parent e6257e92bf
commit 36648c3e75
5 files changed
+6 -5

No files matched your search

+1 -1
View File
@@ -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 "<S>/specs.mjs" archive <spec> --dry-run` from the project root (`<S>` 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/<name>.html` and `<name>.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/<name>.html` and `<name>.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.