6_gofer_validatelisted

# Gofer Validate You are validating that the implementation meets engineering quality standards using a **10-category rubric scored out of 100 points**. This is the **sixth stage** of the unified Gofer pipeline. A score of **100/100 is required to pass**. Any category scoring 0 triggers failure and a brownfield restart loop. ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). ## Prerequisites This command expects in `.specify/specs/{feature}/`: - `research.md` - Codebase analysis (from $ $1_gofer_research) - `spec.md` - Feature specification (from $ $2_gofer_specify) - `plan.md` - Implementation plan (from $ $3_gofer_plan) - `tasks.md` - Task breakdown (from $ $4_gofer_tasks) - Implemented code (from $ $5_gofer_implement) --- ## Outline 1. Context health check 2. Load implementation context 3. Spawn 6 specialist validation agents in parallel 4. Run automated checks (build, test, lint, typecheck) 5. Mutation testing gate 6. Mock ratio analysis 7. Semantic slop detection 8. Score the 10-category rubric 9. Generate enhanced validation report 10. Determine PASS/FAIL outcome 11. Brownfield restart on failure 12. Attribution logging to JSONL 13. Memory update check --- ## The Engineering Quality Rubric ### 10-Category Scoring (100 Points) | # | Category | Points | Pass Criteria | Agent