plan-swarm-review
FeaturedIterative plan review using multisampling + focused decomposition. Launches parallel independent agents to find issues that single-pass review misses. 4 escalating rounds: broad -> multisample -> focused -> focused+multisample. Use when: "swarm review", "review plan thoroughly", "multisample review", "deep plan review", "plan swarming", "stress test the plan", or before implementing any plan >500 lines or with >3 interacting components. Also use proactively when a large plan is about to be implemented — catch issues before code, not after. Do NOT use to design a multi-agent harness or Generator-Evaluator architecture from scratch; use harness-design for that. Do NOT use to review already-written code/diffs; use deep-review for that (this reviews plans, not implementations).
Install
Quality Score: 92/100
Skill Content
Details
- Author
- AnastasiyaW
- Repository
- AnastasiyaW/claude-code-config
- Created
- 4 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
plan-swarm
Socratic planning interview for swarm decomposition
plan-review
Review .context/plans/*.md files using 3 independent subagent reviewers: Technical (feasibility, gaps, soundness), Strategic (scope, alignment, priority), and Risk (blind spots, edge cases, failure modes). The skill FIRST asks the user which models to assign to each reviewer — presenting available options based on the user's environment (OpenCode Zen, Go, Claude Code, or BYOK). Each reviewer receives the same plan with a role-specific lens and returns structured feedback. The main agent consolidates all three perspectives. Triggers: 'review this plan', 'audit plan', 'plan review', 'check my plan', 'what's wrong with this plan', 'review all plans', 'plan quality check'. Do NOT use for plans not in .context/plans/, one-off notes, or external documents.
review-swarm
Local, free, multi-specialist review of a diff: parallel Claude subagents (correctness, security/trust boundaries, data/perf, architecture-altitude, ponytail-simplicity, tests/failure paths), adversarial verification, dedup, ranked file:line report. Use proactively when asked to review, check, or assess a diff, branch, or PR — and after any non-trivial implementation, before the PR. Also on "review-swarm", "swarm review", "deep review". Not for trivial diffs or when asked to fix, not review.