open/ktg-plugin-marketplace
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions

chore(voyage): release v5.0.1 — drop standalone HTML render; print literal /playground document-critique invocation

Browse source 
The v5.0.0 stop-gap had /trekbrief, /trekplan, and /trekreview each render
a read-only {artifact}.html (via scripts/render-artifact.mjs) AND print a
vague "run the /playground plugin" instruction. In practice the read-only
HTML was redundant with what /playground produces and the instruction
wasn't copy-paste-ready — the operator had to guess the right invocation.

v5.0.1 deletes scripts/render-artifact.mjs + its test + npm run render,
and makes each producing command end with a single boxed, literal,
copy-paste-ready line:

    /playground build a document-critique playground for {artifact_path}

One paste from the operator launches the official playground skill's
document-critique template, which builds an interactive HTML — artifact
on the left, per-line Approve/Reject/Comment cards on the right, Copy
Prompt button at the bottom. Mark suggestions, click Copy Prompt, paste
back, Claude revises the .md. Doc-consistency test pins the literal
invocation so the prose cannot soften back into vagueness.

npm test green: 503 tests, 501 pass, 0 fail, 2 skipped.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-05-13 13:24:32 +02:00
commit 2e0892cdaf
15 changed files with 206 additions and 563 deletions
Download patch file Download diff file Expand all files Collapse all files

40
plugins/voyage/commands/trekplan.md
View file

@ -769,28 +769,32 @@ If the user asks questions or requests changes:
- Show what changed
- Re-present the summary
### Render to HTML + link (annotation via /playground)
### Print the annotation invocation
After `plan.md` is final, render it to a self-contained HTML view in the
same project directory and print the `file://` link:
```bash
node ${CLAUDE_PLUGIN_ROOT}/scripts/render-artifact.mjs "{plan_path}"
```
This writes `{plan_dir}/plan.html` — a zero-network, design-system-styled
page (frontmatter folded into a `<details>` block, code fences in styled
`<pre>`). Print:
After the plan summary, print this block **verbatim** (substituting only
`{plan_path}` with the absolute path). The `/playground` command must
appear literally — operators copy-paste it directly into Claude. It
points at the official `claude-plugins-official` `playground` skill,
which loads its `document-critique` template, reads `plan.md`, generates
per-line suggestions, and writes a single self-contained HTML file that
opens in the browser. The HTML has the plan on the left (nicely
formatted, line-numbered), suggestion cards on the right (Approve /
Reject / Comment), and a "Copy Prompt" button at the bottom that gathers
everything marked into one prompt. Paste that prompt back into Claude —
Claude then revises `plan.md` freehand from the notes.
```
Plan rendered: file://{abs path to plan.html}
To annotate: open it, then run the `/playground` plugin
(document-critique template) on plan.md and paste the generated
prompt back here. Claude revises plan.md freehand from your notes.
```
────────────────────────────────────────────────────────────────────
To review and annotate this plan, copy and paste this into Claude:
If `render-artifact.mjs` exits non-zero, surface a one-line warning and
continue — the rendered view is a convenience, not a gate.
/playground build a document-critique playground for {plan_path}
That builds a self-contained HTML file with the plan on the left,
per-line approve/reject/comment annotations on the right, and a
"Copy Prompt" button at the bottom. Copy the generated prompt, paste
it back here, and Claude revises plan.md from your notes.
────────────────────────────────────────────────────────────────────
```
## Phase 11 — Handoff