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>
19 lines
945 B
Markdown
19 lines
945 B
Markdown
---
|
|
description: "Routing case: the annotating skill should fire on this request (the reserve path outside the pipeline)."
|
|
expected_outcome: "Claude calls the Skill tool for voyage:annotating at least once."
|
|
tags: [skill-trigger, skill=annotating, from=baseline-ann-question-edits]
|
|
runs: 3
|
|
max_turns: 4
|
|
allowed_tools: [Read, Glob, Grep, Skill]
|
|
---
|
|
|
|
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 (1 total)
|
|
|
|
### 1. [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?
|