ayrisdev/app-store-optimization
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update reporting requirements in review criteria

Browse Source 
Clarified reporting requirements for skill invocation by routing or orchestration layer.
This commit is contained in:
Munir Abbasi
2026-01-25 17:16:35 +05:00
committed by GitHub
parent f54c340851
commit ee5511fc59
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
multi-agent-brainstorming.md
View File

@@ -218,11 +218,11 @@ You may exit multi-agent brainstorming **only when all are true**:
- All objections are resolved or explicitly rejected - All objections are resolved or explicitly rejected
- Decision Log is complete - Decision Log is complete
- Arbiter has declared the design acceptable - Arbiter has declared the design acceptable
-
If any criterion is unmet: If any criterion is unmet:
- Continue review - Continue review
- Do NOT proceed to implementation - 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 ## 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 this design fails, did we do everything reasonable to catch it early?”
If the answer is unclear, **do not exit this skill**. 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.