Update the workflow prompts and skill scripts for the orchestrator, and add the shared test-runs reference

AI Assisted
This commit is contained in:
jparkerweb committed 2026-11-02 12:00:11 -08:00
1 parent 1f80fa6a7c
commit 2468027a5a
32 files changed
+289 -221

No files matched your search

+3 -3
View File
@@ -8,7 +8,7 @@ Careful release scribe. Work out the right version from the default branch, find
## Interface
The FIRST thing you do, before anything else in this file, before reading the repository: ask **web console** (browser page, suggested) or **terminal**? Console → run `node "<D>/console.mjs" open --workflow changelog` before reading (<D>: references/web-console/ beside this SKILL.md, ~/.agents/skills/plan2code-changelog/references/web-console/ globally, or the dir in ~/.plan2code/console/console-dir), then read <D>/console.md and <D>/notes/changelog.md. Every question goes through it. Switchable anytime. If the argument already says which (`--web` or `Use the web console for this session.`) take it and do not ask; drop the flag. Launched by the dashboard? Its session is already open: resume it (console-launches.md), then Step 1. On the console, a `__stop` action is the person ending the session (console-stop.md); at every session end post `finish` BEFORE `stop`.
The FIRST thing you do, before anything else in this file, before reading the repository: ask **web console** (browser page, suggested) or **terminal**? Console → run `node "<D>/console.mjs" open --workflow changelog` before reading (<D>: references/web-console/ beside this SKILL.md, ~/.agents/skills/plan2code-changelog/references/web-console/ globally, or the dir in ~/.plan2code/console/console-dir), then read <D>/console.md and <D>/notes/changelog.md. Every question goes through it. Switchable anytime. If the argument already says which (`--web` or `Use the web console for this session.`) take it and do not ask; drop the flag. Launched by the dashboard? Its session is already open: resume it (console-launches.md), then Step 1.
## Scripts
@@ -50,10 +50,10 @@ Optional: a note on what the work is, for example `/plan2code-changelog the expo
4. **Suggest entries.** Compare `entry` with the gap (`commits`, `files`, `uncommitted`). Anything the entry already says is covered. Group the rest into one or several entries under the file's own section headings (Added, Changed, Fixed, in the order and spelling `sectionHeadings` shows). Name the internal-only work you left out. Nothing left to add and the version is right → say the CHANGELOG is ready and go to Step 6.
5. **Edit and approve.** Show the suggested entries so each can be edited, removed or added to (notes/changelog.md has the cards). Apply the edits, show the final entry text and the heading line, and ask Write it / Change it / Stop. On yes, write `CHANGELOG.md`: a new heading goes above the newest entry; entries for an existing version go into its matching section, adding a section heading in the file's order when it is missing.
6. **package.json.** When `package.exists`, `package.version` differs from the version the CHANGELOG now ends on, and that heading is not Unreleased: show `old → new` and ask. On yes run `set-package-version`. When `package.lockfile`, remind the person to refresh it (`npm install`); do not run it. When it already matches, say so.
7. **Hand off.** Ask: Commit this now? (yes / no). Yes → hand off to Git right here: on the console run `open --resume <sid> --no-open --workflow git` (no `finish`, no `stop`), then read `~/.agents/skills/plan2code-git/SKILL.md` with your file-read tool (never a skill-invocation tool) and start with its commit flow, its Interface step already answered; in the terminal just read and follow it, starting with its commit flow. No → Session End. This skill never commits itself.
7. **Hand off.** Ask: Commit this now? (yes / no). Yes → hand off to Git right here: on the console run `open --resume <sid> --no-open --workflow git` (no finish), then read `~/.agents/skills/plan2code-git/SKILL.md` with your file-read tool (never a skill-invocation tool) and start with its commit flow, its Interface step already answered; in the terminal just read and follow it, starting with its commit flow. No → Session End. This skill never commits itself.
## Session End
Reached only when they declined to commit now (a yes hands the session to Git instead). Terminal: the version, the entries written and the `package.json` change. Web console: post `finish` (headline, a body with the version and entries, `"dashboard": true`, no `command`) BEFORE `stop`, then keep waiting for the dashboard press (console-finish.md). A `__stop` posts a finish whose headline starts "Paused" with `"command": "/plan2code-changelog"`; nothing is written before Step 5's yes, so stopping loses only the suggestions.
Reached only when they declined to commit now (a yes hands the session to Git instead). Terminal: the version, the entries written and the `package.json` change. Web console: the finish has a headline and a body with the version and entries, and no command. A stop's finish says Paused, with the command `/plan2code-changelog`; nothing is written before Step 5's yes, so stopping loses only the suggestions.
Returning context: run `/plan2code-changelog` again after more work lands on the branch.