What problem does it solve?
It prevents false confidence in bench testing by enforcing that journey changes in the gentle-ai bench corpus are proven through driven harness execution rather than relying on go test ./bench, which only validates corpus declarations.
Core Features & Use Cases
- Journey Authoring Rules: Enforces unique journey IDs across all
journeys_*.go files, mandatory Review: declarations (reviewOptedIn or reviewUntouched), and runnable commands on every execute transition.
- CI-Faithful Verification: Requires reading the Unit Tests step in
.github/workflows/ci.yml and reproducing its exact build and gentle-ai-bench run --binary ... commands, with --only <journey-id> for single journeys.
- Semantic Change Auditing: When a ratified product semantic changes, greps the corpus for journeys pinning the old behavior so stale assertions do not keep defects green.
- Use Case: When adding a new bench journey or diagnosing a bench failure in CI, load this Skill to author the journey correctly, run both declaration tests and the driven harness, and include the driven-mode summary line in the PR body.
Quick Start
Load this skill before editing anything under bench/ in gentle-ai, then follow its rules to author the journey and prove it with the driven harness against a locally built binary.