From ee5511fc596395f69a469536aa7f54e651f9368a Mon Sep 17 00:00:00 2001 From: Munir Abbasi Date: Sun, 25 Jan 2026 17:16:35 +0500 Subject: [PATCH] Update reporting requirements in review criteria Clarified reporting requirements for skill invocation by routing or orchestration layer. --- multi-agent-brainstorming.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/multi-agent-brainstorming.md b/multi-agent-brainstorming.md index 7807428d..acda9e98 100644 --- a/multi-agent-brainstorming.md +++ b/multi-agent-brainstorming.md @@ -218,11 +218,11 @@ You may exit multi-agent brainstorming **only when all are true**: - All objections are resolved or explicitly rejected - Decision Log is complete - Arbiter has declared the design acceptable - +- If any criterion is unmet: - Continue review - Do NOT proceed to implementation - +If this skill was invoked by a routing or orchestration layer, you MUST report the final disposition explicitly as one of: APPROVED, REVISE, or REJECT, with a brief rationale. --- ## Failure Modes This Skill Prevents @@ -253,4 +253,4 @@ This skill exists to answer one question with confidence: > “If this design fails, did we do everything reasonable to catch it early?” If the answer is unclear, **do not exit this skill**. -If this skill was invoked by a routing or orchestration layer, you MUST report the final disposition explicitly as one of: APPROVED, REVISE, or REJECT, with a brief rationale. +