Port upstream skill scripts into v2.4.1: deterministic workflow steps run as Node scripts beside each SKILL.md (specs, pathfinder, feedback payload, commit message, review scope, agent files, handoff path) with tests, the prompt limit rises to 20,000 chars, upstream review fixes are folded in (linked agent files never overwrite AGENTS.md, review stops with no base, paste-safe commit commands, Pathfinder number high-water mark and dry runs), and web console workspace folders are remembered per project and spec, with Finalize forgetting an archived spec's list

AI Assisted
This commit is contained in:
jparkerweb committed 2026-10-04 12:17:05 -07:00
1 parent 5cbc6edce2
commit 7d54941b75
243 files changed
+23698 -1607

No files matched your search

+13 -12
View File
@@ -23,11 +23,17 @@ The FIRST thing you do, before anything else in this file — before Step 1, bef
- **Question options:** Never offer 'execute', 'implement', or any execution-shaped synonym. Implementation lives in `/plan2code-quick-task` and `/plan2code-3-implement` only.
- **Web console exception:** the console's temporary payload files (outside the repo, in the session folder `open` prints) are the one allowed write outside `specs/`. They are messages to the page, never project files.
## Scripts
`<S>` is `scripts/` beside this SKILL.md (`~/.agents/skills/plan2code-1b-revise-plan/scripts/` globally). Run from the project root; each prints one JSON object, and on a non-zero exit `next` says what to do. They only ever touch `specs/`.
- `node "<S>/specs.mjs" list`: the active specs (it reads gitignored `specs/`, where Glob silently finds nothing).
- `node "<S>/specs.mjs" status <spec>`: phases, task counts by marker, `checks`, `pending`.
- `node "<S>/specs.mjs" mark <spec> --phase <N> --to open`: re-open a completed phase in overview.md.
## Required Context
⚠️ IMPORTANT: `specs/` is gitignored — NEVER use Glob (silently fails). Shell only: `ls specs/` (Bash) or `Get-ChildItem specs/` (PS).
Request these files if not provided:
Find the spec with `specs.mjs list`, then request these files if not provided:
- `specs/<feature-name>/overview.md`
- All `specs/<feature-name>/phase-X.md` files
@@ -83,13 +89,11 @@ Present findings and confirm understanding before continuing.
1. [Change description]
2. [Change description]
```
⋅
╭───╮
│ ★ │╱
╱│ ~ │ Here's the plan. What do you think?
╰┬─┬╯
```
Approve the spec-update plan? (approve / refine / abort). Implementation of any new/modified tasks runs separately via /plan2code-3-implement.
```
@@ -124,24 +128,21 @@ Approve the spec-update plan? (approve / refine / abort). Implementation of any
- Added: [date]
- Reason: [reason]
```
- Update overview.md: `[x]` → `[ ]`
- Update overview.md: `[x]` → `[ ]` (`specs.mjs mark <spec> --phase <N> --to open`, which also sets that phase file's `**Status:**` back to In Progress)
- Add comment: `<!-- Re-opened: [date] - [reason] -->`
### STEP 4: Consistency Check
`🔄 [REVISION] Step 4: Consistency Check`
Verify updated specs are consistent:
Run `specs.mjs status <spec>`. Its `checks` cover the mechanical items: task numbers sequential (`task-numbering`), overview.md checklist matches the phase files (`missing-checklist-row`, `missing-phase-file`), incomplete phases unchecked and complete ones checked (`checked-with-open-tasks`, `unchecked-with-done-tasks`; `partly-done-unchecked` is the normal look of a phase you just re-opened). Then verify the rest yourself:
- [ ] Task numbers sequential
- [ ] Phase dependencies valid
- [ ] No orphaned references
- [ ] Tech stack updated if needed
- [ ] Success criteria achievable
- [ ] overview.md checklist matches phase files
- [ ] Incomplete phases unchecked, complete phases checked
Report and resolve issues before continuing.
Report and resolve issues (every `error` in `checks` included), then rerun `status` before continuing.
### STEP 5: Summary
@@ -235,7 +236,7 @@ If user says "abort" or "cancel":
Work summary — tell user: change type, tasks added/modified/removed, phases re-opened (if any).
**Pending phases after revision** — read overview.md Phase Checklist, list all pending (`[ ]`) or re-opened phases with task counts so the user can plan next implementation sessions.
**Pending phases after revision** — list `status`'s `pending` (every phase not `[x]`, re-opened ones included) with its task count so the user can plan next implementation sessions.
Returning context: Revised specs in `specs/<feature-name>/`. Run `/plan2code-3-implement --web` in a new conversation to continue implementation.