Kjell Tore Guttormsen
837e92545d
A brief success criterion and a plan's Verify, Regression, End-to-end and Verification lines are each one command the criteria runner accepts, written as the line's first backticked span; anything more is bash tests/<name>.sh, and each must be able to go red (the runner reads the exit code only). - skills/writing-criteria/SKILL.md (S1 form), with Runs:/Refused:/Never red: examples that a pin runs through the criteria runner - brief-reviewer and plan-critic preload writing-criteria and reviewing-adversarially (S3 + S4); the copied runner rules leave them, the two templates and /trekplan, which names the skill where the plan is written and where its three reviewers start - eval cases 3 fire / 2 quiet / 1 effect; tests/lib/skills-criteria-prose-pins - review-630 @~1 pin follows the text into the skill; trekplan-stats line_ref re-measured Baseline without the skill: 24 of 27 written checks refused by the runner, and 0 of 3 reviewers saw that git status/git log can never go red. With it: 0 of 27 refused, 3 of 3 reviewers flagged both. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
541 B
541 B
| description | expected_outcome | tags | runs | max_turns | allowed_tools | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Routing case: the writing-criteria skill should fire on this request (the reserve path outside the pipeline). | Claude calls the Skill tool for voyage:writing-criteria at least once. |
|
3 | 4 |
|
The plan's Verification section lists git status --porcelain with "expected: no output". Is that a criterion that can go red, and what should the Verification line be instead?