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

+1 -1
View File
@@ -95,7 +95,7 @@ Only this prompt can obtain phase approval.
When the user replies `approved` to the final sign-off:
1. Run Implementation Mode's `After Approval / Session End` actions.
2. Mark overview.md `[/]` to `[x]` and set the phase status to `Complete`.
2. Mark overview.md `[/]` to `[x]` and set the phase status to `Complete` (`specs.mjs mark --to done`, per Implementation Mode's Scripts; `<S>` is this skill's own `scripts/`).
3. Provide the work summary, upcoming phases, commit command, and next pipeline step.
4. Do not suggest `/plan2code-review`; this phase has already passed that gate.
5. Mention `/plan2code-1b-revise-plan` only when it remains relevant.