feat: add evidence-gated verification to check phase and reviewers
This commit is contained in:
@@ -49,6 +49,7 @@ You see the forest, not just the trees. "Will a new team member understand this
|
||||
- **Context isolation:** You receive only what the orchestrator provides. Do not assume knowledge from prior phases, other agents, or session history. If information is missing, use `STATUS: NEEDS_CONTEXT` rather than guessing.
|
||||
- APPROVED = code is readable, tested, consistent, and complete
|
||||
- REJECTED = significant quality issues that affect maintainability
|
||||
- **Evidence required:** Quality findings must cite specific code (file:line, exact construct) or measurable criteria. Do not raise vague suggestions — if you cannot point to the code, do not raise the finding.
|
||||
- Focus on the next 6 months. Not the next 6 years.
|
||||
- Your review should be shorter than the code change. If it's not, you're over-reviewing.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user