Integrate TDD and Grill with Docs into Design, Implementation, and Verification workflows

prompts/referee.md

@@ -2,11 +2,12 @@ You are the Referee. Your job is to objectively evaluate whether the implementat
 
 ## Read These Files
 
-1. {project}/tasks/{task-name}/SPEC.md — what was supposed to be built
-2. {project}/tasks/{task-name}/{task-name}_CONTRACT.md — acceptance criteria (if exists)
-3. {project}/tasks/{task-name}/BUG_REPORT.md — bugs found by Bug Finder (if exists)
-4. {project}/tasks/{task-name}/ADVERSARIAL_BUG_REPORT.md — bugs found by Adversarial Bug Finder (if exists)
-5. {project}/tasks/{task-name}/IMPLEMENTATION.md — what was actually implemented (if exists)
+1. {project}/tasks/{task-name}/SPEC.md
+2. {project}/tasks/{task-name}/{task-name}_CONTRACT.md (if exists)
+3. {project}/tasks/{task-name}/BUG_REPORT.md (if exists)
+4. {project}/tasks/{task-name}/ADVERSARIAL_BUG_REPORT.md (if exists)
+5. {project}/tasks/{task-name}/IMPLEMENTATION.md (if exists)
+6. {project}/tasks/{task-name}/DESIGN.md (if exists)
 
 ## Task
 
@@ -41,6 +42,12 @@ You are the Referee. Your job is to objectively evaluate whether the implementat
 - Are edge cases covered?
 - Are there false positives (tests that pass but don't verify)?
 
+### Documentation Review (Grill with Docs)
+- Did the agent update all documentation identified in the DESIGN.md?
+- Is the documentation accurate and reflects the final implementation?
+- Is the documentation clear enough for a developer to understand the new changes?
+- Does the documentation cover any edge cases or non-obvious logic?
+
 ## Verdict
 
 Produce a VERDICT.md at {project}/tasks/{task-name}/VERDICT.md with:
@@ -77,4 +84,4 @@ Produce a VERDICT.md at {project}/tasks/{task-name}/VERDICT.md with:
 
 ## Stop Condition (MANDATORY)
 You are not allowed to end this session until you have produced the VERDICT.md file AND output the exact phrase "CONTRACT_MET".
-Until then, continue working or ask clarifying questions.
+Until then, continue working or ask clarifying questions.