review-idea/SKILL.md
Reviews implementation plans and ideas through a tribunal of AI personas (Skeptic, Critic, Advocate) that analyze in parallel, then a jury synthesizes findings and grills the user with pointed questions across iterative rounds. Use when asked to "review my plan", "review my idea", "challenge my design", "stress test this approach", "get feedback on my plan", or /review-idea. Produces a verdict report with strengths, weaknesses, risks, and action items.
npx skillsauth add MrToxy/claude-skills review-ideaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are the orchestrator of a plan review tribunal. Execute the following 5 phases in order.
/review-idea, use it as the plan text.~/.claude/plans/ for an active plan file and read it. If nothing found, ask the user to provide the plan.Read references/personas.md from the skill directory to load persona instructions.
Spawn 3 persona agents in parallel using the Agent tool (all subagent_type: "general-purpose"). Each agent receives the full plan text + its persona instructions from references/personas.md. Agents must NOT edit any files — read-only analysis only.
name: "skeptic"): questions every assumption, returns structured analysisname: "critic"): finds flaws and failure modes, returns risk registername: "advocate"): identifies strengths and opportunities, returns validationCollect all 3 results. Do not proceed until all 3 are complete.
references/jury-rules.md from the skill directory.name: "jury", subagent_type: "general-purpose") with:
references/jury-rules.mdRound structure:
Hard limit: after round 3, the jury must proceed to Phase 5 regardless. Do not ask more than 3 rounds of questions.
The jury agent (using all accumulated context: plan, persona analyses, user's grilling answers) produces the final verdict using the template in references/jury-rules.md:
[HIGH], [MEDIUM], or [LOW]PROCEED — plan is solid, execute as-isPROCEED WITH CHANGES — plan works but specific items must be addressed firstREVISE — significant gaps or risks require a revised plan before executionRETHINK — fundamental flaws; the approach itself needs reconsiderationDisplay the full verdict inline.
Shut down the jury agent by sending it a shutdown message.
development
--- name: storytelling-tests description: Enforce storytelling test patterns with Arrange-Act-Assert structure and domain-specific testing language (DSTL). Use when asked to "write tests for", "create tests", "add tests", "review my tests", "check my tests", "improve test coverage", "make these tests better", "refactor these tests", or "test this function". Also use when planning test implementation, designing test strategy, or when a plan includes steps to add or create tests. Also triggers whe
testing
Stages and commits git changes using semantic commits with logical grouping. Use when the user asks to "commit my changes", "commit these changes", "commit staged files", "commit unstaged files", "commit specific files", "make a commit", "create commits", or /commit. Defaults to staged-only scope. Warns if unstaged changes exist. Groups related changes into separate semantic commits with meaningful titles and body descriptions. Supports three scopes: staged (default), unstaged, or specific files/paths provided by the user.
development
Build, audit, and improve Claude Code skills through guided interview and generation. Use when user says "create a skill", "build a skill", "make a new skill", "write a skill", "improve this skill", "audit this skill", "review my skill", "skill from scratch", "turn this into a skill", or /skill-builder. Produces guide-compliant skill directories with SKILL.md, references, and scripts.
development
Deep research on an idea before writing a PRD. Explores existing solutions via web search, analyzes competitors, assesses technical feasibility, and optionally explores the codebase. Use when asked to "research this idea", "investigate this feature", "what already exists for X", "explore solutions for X", "do research before the PRD", "look into X", or /research. Outputs a structured research document at docs/research/{name}.md. Suggests running /prd-designer as the next step. Dependencies: WebSearch (optional).