cross-critique
Run a second round on a contested question by circulating each subagent's independent proposal to the other authors and asking for structured pros and cons, then synthesize. Use this skill whenever you have multiple independent proposals or opinions on a contested decision — architecture tradeoffs, code review disagreements, design choices, competing root-cause theories — and want sharper analysis than you'd produce by synthesizing alone. Pairs naturally with the council and research skills; reach for it liberally whenever proposals diverge.
Install
With your agent
Install OMGSkills skill "warpdotdev/common-skills:cross-critique" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/warpdotdev/common-skills /tmp/common-skills && ln -s /tmp/common-skills/.agents/skills/cross-critique ~/.claude/skills/cross-critiqueFrom README
Cross-Critique Use this skill to run a second round after several subagents have independently produced proposals or opinions on the same contested question. Instead of synthesizing their reports yourself, you circulate each proposal to the other authors and ask them to critique it — pros and cons — and then you synthesize the richer set of analyses that results. Why this matters When you generate independent proposals (different models, different angles), each author ends up with deep context on the question — often deeper than yours, since they did the investigation. If you jump straight to synthesizing their reports alone, you're the bottleneck: you can only see the tradeoffs you happen to notice.
More from this repo
brandalf
Guides creation, revision, and review of Warp- or Oz-branded assets.
check-impl-against-spec
Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into...
complain
Autonomously yeet a brief, anonymous, completely unstructured complaint into Slack whenever an agent feels frustrated...