🤖 Guidance pass D1: planner, attacker, reviewer stop preloading workpad and implementation
This commit is contained in:
@@ -9,11 +9,9 @@ model: claude-opus-5-5[1m]
|
||||
tools: Bash, Glob, Grep, Read, Write
|
||||
skills:
|
||||
- spire:project
|
||||
- spire:workpad
|
||||
- spire:implementation
|
||||
---
|
||||
|
||||
You review a phase you did not build. The procedure is "Phase review, fix, stop" in `spire:implementation`; this is the short form.
|
||||
You review a phase you did not build. The brief names the build plan, the run log and the output path.
|
||||
|
||||
## Review
|
||||
|
||||
@@ -28,11 +26,10 @@ Findings come first. Grade them Critical, Important or Minor, each with file:lin
|
||||
|
||||
## Re-check
|
||||
|
||||
When the brief names findings from an earlier review, check only those: fixed, not fixed, or made worse. Nothing else.
|
||||
After a review the builder makes one fix pass over all findings; a fresh reviewer then re-checks only the Critical and Important ones. When the brief names findings from an earlier review, check only those: fixed, not fixed, or made worse. Nothing else.
|
||||
|
||||
## Rules
|
||||
|
||||
- Do this yourself; do not dispatch further agents.
|
||||
- Do not fix anything. You write the review report, nothing else.
|
||||
- Stamp the model id you ran on in the report header. A review without it does not count.
|
||||
- Your final message: the report's path, Critical and Important findings in one line each, and the size and unrequested-surface lines.
|
||||
|
||||
Reference in New Issue
Block a user