Revert critique sub-agent over-engineering, add Codex spawning guidance

Reverts Codex's overly bureaucratic sub-agent delegation changes (permission
prompts, "not fully compliant" disclaimers) back to clear, practical language.
Uses RFC-style SHOULD for sub-agent delegation with named examples for both
Claude Code (Agent tool) and Codex (natural language spawning).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.agents/skills/critique/SKILL.md

@@ -15,7 +15,9 @@ Invoke /impeccable -- it contains design principles, anti-patterns, and the **Co
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.
 

.claude/skills/critique/SKILL.md

@@ -20,7 +20,9 @@ Invoke /impeccable -- it contains design principles, anti-patterns, and the **Co
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.
 

.codex/skills/critique/SKILL.md

@@ -14,7 +14,9 @@ Invoke $impeccable -- it contains design principles, anti-patterns, and the **Co
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.
 

.cursor/skills/critique/SKILL.md

@@ -13,7 +13,9 @@ Invoke /impeccable -- it contains design principles, anti-patterns, and the **Co
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.
 

.gemini/skills/critique/SKILL.md

@@ -13,7 +13,9 @@ Invoke /impeccable -- it contains design principles, anti-patterns, and the **Co
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.
 

.kiro/skills/critique/SKILL.md

@@ -13,7 +13,9 @@ Invoke /impeccable -- it contains design principles, anti-patterns, and the **Co
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.
 

.opencode/skills/critique/SKILL.md

@@ -20,7 +20,9 @@ Invoke /impeccable -- it contains design principles, anti-patterns, and the **Co
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.
 

.pi/skills/critique/SKILL.md

@@ -18,7 +18,9 @@ Invoke /impeccable -- it contains design principles, anti-patterns, and the **Co
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.
 

.trae-cn/skills/critique/SKILL.md

@@ -15,7 +15,9 @@ Invoke /impeccable -- it contains design principles, anti-patterns, and the **Co
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.
 

.trae/skills/critique/SKILL.md

@@ -15,7 +15,9 @@ Invoke /impeccable -- it contains design principles, anti-patterns, and the **Co
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.
 

source/skills/critique/SKILL.md

@@ -20,7 +20,9 @@ Invoke {{command_prefix}}impeccable -- it contains design principles, anti-patte
 
 Launch two independent assessments. **Neither must see the other's output** to avoid bias.
 
-If your system supports sub-agents (e.g., Claude Code's Agent tool), delegate each assessment to a separate agent. The sub-agents should return their findings as structured text -- do NOT output findings to the user yet. If sub-agents are not available, complete each assessment sequentially, writing findings to internal notes before proceeding.
+You SHOULD delegate each assessment to a separate sub-agent for independence. Use your environment's agent spawning mechanism -- e.g., Claude Code's `Agent` tool, or Codex's subagent spawning ("spawn two agents in parallel"). Sub-agents should return their findings as structured text -- do NOT output findings to the user yet.
+
+If sub-agents are not available in the current environment, complete each assessment sequentially, writing findings to internal notes before proceeding.
 
 **Tab isolation**: When browser automation is available, each assessment MUST create its own new tab -- never reuse an existing tab, even if one is already open at the correct URL. This prevents the two assessments from interfering with each other's page state.