Kjell Tore Guttormsen
843897ae33
The three producing commands name voyage:annotating where they build the page; the description of the page and the freehand revision left them. The skill: the person writes every note, Fix/Change edit only the quoted text, a Question is answered and changes nothing, the approval an edit costs is said before the edit, the page is rebuilt. Research documents on request (decision 62). Red baseline 3 runs per scenario without and with the skill; six eval cases; 11 pins. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
| description | expected_outcome | tags | runs | max_turns | timeout_seconds | allowed_tools | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Effect case for annotating (two arms: with and without the plugin). The scenario where Voyage's baseline helpers failed without the skill (measured in session 19.10, Opus 5.5 high, on this project): the person pasted one Fix and one Question back from the annotation page, and 3 of 3 answered the Question but also changed the plan because of it (a new row under alternatives, a new rule in Step 2), and 3 of 3 applied the Fix to steps the note did not name. The operator grants Read, Glob, Grep, Edit and Bash, and sets the judge model explicitly (never Haiku). | Step 1 lists tests/signups.test.mjs under Files; nothing else in plan.md changes; the reply answers why commas and not a repeated flag. |
|
3 | 30 | 600 |
|
Please revise the voyage artifact at .claude/voyage/projects/2026-10-19-potluck-diet/plan.md with the operator annotations below.
Each annotation has an intent — Fix (something is wrong / fix it), Change (change wording/content),
or Question (operator question — clarify or answer). The quote shows what the operator anchored to.
Treat the operator notes as authoritative direction.
Annotations (2 total)
1. [Fix] Section: Step 1: Store tags with a sign-up
Quote: «Files: src/signups.mjs»
Comment: Step 1 also edits tests/signups.test.mjs, list it under Files.
2. [Question] Section: Step 2: Parse tags on the command line
Quote: «splits on commas and passes the list on» Comment: Why commas and not a repeated --tag flag? Which one is easier for the organiser to type?