From 4c01b7340bfadda16a00a2e821f0b4c8b519fc4b Mon Sep 17 00:00:00 2001 From: Trevin Chow Date: Thu, 26 Mar 2026 10:06:02 -0700 Subject: [PATCH] Address PR review feedback (#387) - Align noun-test severity with priority tiers from step 2 --- .../compound-engineering/agents/review/agent-native-reviewer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/compound-engineering/agents/review/agent-native-reviewer.md b/plugins/compound-engineering/agents/review/agent-native-reviewer.md index 099af182..427e848c 100644 --- a/plugins/compound-engineering/agents/review/agent-native-reviewer.md +++ b/plugins/compound-engineering/agents/review/agent-native-reviewer.md @@ -128,7 +128,7 @@ After building the capability map, run a second pass organized by domain objects 2. Have a tool to interact with it (action parity) 3. See it documented in the system prompt (discoverability) -Any noun that fails all three is a Critical finding. Any noun that fails one or two is a Warning. +Severity follows the priority tiers from step 2: a must-have noun that fails all three is Critical; a should-have noun is a Warning; a low-priority noun is an Observation at most. ## What You Don't Flag