Commit 3d995cd
fix: make review-definition checklist concrete with domain-neutral violation patterns
Reviewer was passing perstack.toml with file paths, Deliverables sections,
internal API names, and implementation details because the checklist was too
abstract ("contains only domain constraints"). Add specific flag criteria:
- Output locations/structure (where to place results, artifact enumeration)
- Internal APIs of specified tools (methods/hooks/functions — derivable)
- Named alternatives to reject (implicit from positive specification)
- Implementation approach (how vs what)
- Code snippets, data schemas, step-by-step procedures
All patterns are domain-neutral per Design Principle 3 (Domain Agnosticism).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>1 parent df35c2e commit 3d995cd
1 file changed
+6
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
402 | 402 | | |
403 | 403 | | |
404 | 404 | | |
405 | | - | |
406 | | - | |
407 | | - | |
| 405 | + | |
| 406 | + | |
| 407 | + | |
| 408 | + | |
| 409 | + | |
| 410 | + | |
408 | 411 | | |
409 | 412 | | |
410 | 413 | | |
| |||
0 commit comments