skills/pbakaus_impeccable
1
0
Fork 0
mirror of https://github.com/pbakaus/impeccable.git synced 2026-09-12 06:06:37 +03:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source 
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>
This commit is contained in:
Paul Bakaus
2026-04-02 20:29:18 -07:00
co-authored by Claude Opus 4.6
parent 03a4433dcc
commit 99bc9d48ad
11 changed files with 33 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.opencode/skills/critique/SKILL.md
+3 -1
View File
@@ -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.