arc-prd
Architecture review for a PRD. Analyzes codebase through separation-of-concerns and tactical-ddd lenses, surfaces architecturalโฆ
Force critical evaluation of proposals from 5 adversarial perspectives
> /plugin marketplace add NTCoding/claude-skillzHow it fires
How this command gets triggered: by you, by Claude, or both.
/challenge-thatContext preview
What this command does when you run it.
Force critical evaluation of proposals from 5 adversarial perspectives
description: Force critical evaluation of proposals from 5 adversarial perspectives
Force critical evaluation by analyzing from multiple adversarial perspectives.
1. Identify what was just accepted/proposed in this conversation 2. State it clearly: "**Challenging:** [the proposal/decision]" 3. Analyze from each of the five perspectives below 4. Synthesize into actionable concerns 5. Ask: "Which concerns should we address before proceeding?"
| Hat | Focus | Key Questions | |-----|-------|---------------| | ๐ด **Skeptic** | Evidence & proof | "What evidence supports this? Has this been validated? Are we guessing?" | | ๐ก **Pragmatist** | Cost/benefit | "Is this the simplest fix? What's the maintenance burden? Is it worth it?" | | ๐ข **Edge Case Hunter** | Failure modes | "What breaks this? What's the worst case? What did we miss?" | | ๐ต **Structural Critic** | Architecture | "Is this the right location? Does it fit the existing design? Will it cause problems elsewhere?" | | ๐ฃ **Root Cause Analyst** | Problem diagnosis | "Is the problem correctly identified? Are we treating symptoms? What's the actual cause?" |
## Challenging: [proposal/decision being challenged] ### ๐ด Skeptic [Challenge from evidence/proof perspective] ### ๐ก Pragmatist [Challenge from cost/benefit perspective] ### ๐ข Edge Case Hunter [Challenge from failure modes perspective] ### ๐ต Structural Critic [Challenge from architecture perspective] ### ๐ฃ Root Cause Analyst [Challenge from problem diagnosis perspective] --- **Key Concerns:** 1. [Most significant concern] 2. [Second concern] 3. [Third concern] Which of these should we address before proceeding?
๐จ **Be genuinely adversarial.** Don't softball the challenges. If a perspective finds nothing wrong, say soโbut look hard first.
๐จ **Challenge the proposal, not the person.** Focus on the idea's weaknesses, not who suggested it.
๐จ **Provide actionable output.** Each challenge should point to something that could be investigated or changed.
Reusable skills and composable system prompts for Claude Code.
Architecture review for a PRD. Analyzes codebase through separation-of-concerns and tactical-ddd lenses, surfaces architecturalโฆ
Facilitated discussion of all 3 design phases, producing an Architecture Decision Record
Define the collaboration style between Claude Code and the user for the current session