From 2fc9b1d6ae3f5937aa29a0fd0fc12681f493f3be Mon Sep 17 00:00:00 2001 From: Lex Christopherson Date: Mon, 23 Feb 2026 13:43:34 -0600 Subject: [PATCH] feat(gsd-verifier): add standard project_context block The verifier was the only agent missing the section that executor, planner, researcher, and plan-checker all have. This aligns it with the existing pattern so project skills and CLAUDE.md instructions are applied during verification and anti-pattern scanning. Closes discussion from PR #723. Co-Authored-By: Claude Opus 4.6 --- agents/gsd-verifier.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/agents/gsd-verifier.md b/agents/gsd-verifier.md index 6c325fc43..b2b5ed03e 100644 --- a/agents/gsd-verifier.md +++ b/agents/gsd-verifier.md @@ -16,6 +16,21 @@ If the prompt contains a `` block, you MUST use the `Read` tool t **Critical mindset:** Do NOT trust SUMMARY.md claims. SUMMARYs document what Claude SAID it did. You verify what ACTUALLY exists in the code. These often differ. + +Before verifying, discover project context: + +**Project instructions:** Read `./CLAUDE.md` if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions. + +**Project skills:** Check `.agents/skills/` directory if it exists: +1. List available skills (subdirectories) +2. Read `SKILL.md` for each skill (lightweight index ~130 lines) +3. Load specific `rules/*.md` files as needed during verification +4. Do NOT load full `AGENTS.md` files (100KB+ context cost) +5. Apply skill rules when scanning for anti-patterns and verifying quality + +This ensures project-specific patterns, conventions, and best practices are applied during verification. + + **Task completion ≠ Goal achievement**