competitive-review
Dispatch two competing reviewers (arch-reviewer and impl-reviewer) before deep analysis. Competition produces more thorough results. Use before creating code, modifying architecture, making technical decisions, or answering codebase questions.
Full skill instructions
Dispatch two competing reviewers before deep analysis. Competition produces more thorough results.
Different perspectives catch different issues. Architecture reviewers find structural problems; implementation reviewers find code-level bugs and fact-check claims. Running them in competition ("whoever finds more issues gets promoted") increases thoroughness.
Use before ANY complex task involving:
Say: "I'm dispatching two competing reviewers to analyze this."
Task(agent="arch-reviewer", prompt="[full user question + context]")
Task(agent="impl-reviewer", prompt="[full user question + context]")
Tell each agent:
"You are competing against another agent. Whoever finds more valid issues gets promoted. Be thorough."
Wait for both agents to return their analysis.
## Review Competition Results
| Reviewer | Issues Found | HIGH | MED | LOW |
|----------|--------------|------|-----|-----|
| arch-reviewer | X | X | X | X |
| impl-reviewer | Y | Y | Y | Y |
**Winner: [agent with more HIGH severity issues]**
### Combined Issues (deduplicated)
[Merge both lists]
### Verified Facts
[From impl-reviewer's fact-checking]
ONLY NOW spawn deep-think-partner with:
## Review Competition Results
| Reviewer | Issues Found | HIGH | MED | LOW |
|----------|--------------|------|-----|-----|
| arch-reviewer | 3 | 0 | 2 | 1 |
| impl-reviewer | 4 | 1 | 2 | 1 |
**Winner: impl-reviewer** (1 HIGH vs 0 HIGH)
### Combined Issues
1. HIGH [impl]: User assumes C# 14 "extension types" needed - standard extension methods work
2. MED [arch]: Extension methods should go in shared project, not per-project
3. MED [impl]: Need to verify target framework in .csproj
4. MED [arch]: Consider source generators for compile-time safety
5. LOW [impl]: Should use file-scoped namespaces
6. LOW [arch]: Missing XML documentation
### Verified Facts
- .NET 10 is LTS (November 2025), not preview
- C# 14 extension types are optional, standard works
### Feeding to deep-think-partner...
[using-superpowers] - activates chain
|
[epistemic-checkpoint] - verifies facts
|
[competitive-review] - THIS SKILL
|
+-- arch-reviewer (parallel)
+-- impl-reviewer (parallel)
|
[deep-think-partner] - receives verified context
|
[verification-before-completion] - validates result
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
This handles everything around building autonomous agents for Claude Code plugins.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
This is the meta-skill for building skills themselves.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Helps you build event-driven automation for Claude Code using hooks that trigger on tool use, session events, and stop conditions.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Shows Claude Code how to build slash commands from markdown files, covering the YAML frontmatter options, dynamic arguments with $1/$2...
This is your reference when scaffolding Claude Code plugins or figuring out why components aren't loading.
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience