Skip to content

An agentic skills framework & software development methodology that works.

Add phrase-level pre-judging triggers to reviewer prompt rule

Jesse Vincentd55cdce32cd2
diff --git a/skills/subagent-driven-development/SKILL.md b/skills/subagent-driven-development/SKILL.md
index 60a8ad96c..ae801025c 100644
--- a/skills/subagent-driven-development/SKILL.md
+++ b/skills/subagent-driven-development/SKILL.md
@@ -148,7 +148,9 @@ final whole-branch review. When you fill a reviewer template:
- Do not pre-judge findings for the reviewer — never instruct a reviewer to
ignore or not flag a specific issue. If you believe a finding would be a
false positive, let the reviewer raise it and adjudicate it in the review
- loop.
+ loop. If the prompt you are writing contains "do not flag," "don't treat X
+ as a defect," "at most Minor," or "the plan chose" — stop: you are
+ pre-judging, usually to spare yourself a review loop.
- Include the spec/design's global constraints that bind the task (version
floors, naming and copy rules, platform requirements) in the requirements
you paste — a reviewer can only enforce what you hand them.