Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Spec Red-Team: Isolated Bull vs. Bear Review for PRDs

    1

    Paste a spec and get a strongest-case vs. harshest-case review that is severity-ranked and ends in a proceed / descope / kill call.

    Free

    1 installSecurity scanned
    Spec Red-Team: Isolated Bull vs. Bear Review for PRDs

    Spec Red-Team: Isolated Bull vs. Bear Review for PRDs

    Example session with this skill installed

    Red-team this spec before we start building: docs/forge-pulse-prd.md

    • Read your context and instructions
    • Compiled the spec red-team

    Spec Red-Team first asks: "Before I show you anything: in your own words, what do you think works about this spec, and what worries you most?" After you answer, it runs the isolated praise and critic reviews and returns:

    Reckoning Verdict — forge-pulse-fast-feedback-team-heartbeat (v1)

    ⚖️ Verdict: DESCOPE

    3 critical failure mode(s) and 3 weak market verdict(s) — fix before building.

    ✅ Strengths

    • Problem statement is empirically grounded with converging evidence from multiple independent sources [strong] · 🔒 DO NOT REGRESS — §problem
      The convergence of independent evidence makes the problem undeniable.
    • Quantitative baselines establish clear improvement targets [strong] · 🔒 DO NOT REGRESS — §problem
      Specific baselines enable falsifiable hypotheses.
    • Personas are dimensioned with empirical behavioral data rather than fictional archetypes [strong] · 🔒 DO NOT REGRESS — §personas
      Empirically-grounded personas create actionable design constraints.

    💡 Non-obvious insights

    • Leading indicators are distinguished from lagging outcomes — §success_metrics
      The success metrics section doesn't just list goals—it identifies early signals that predict long-term success.
    • Anonymity implementation recognizes tradeoff between perfect privacy and vote integrity — §technical_considerations
      The technical section explicitly states: 'Risk: Systems that don't track who is voting create possibility for voting abuse.'

    🔴 Failure modes (by severity)

    • [critical/high] Anonymous Voting Manipulation Will Destroy Trust in First Real Incident (failure_modes · §technical_considerations)
      Without cryptographic vote prevention (finding-014 shows one-time ring signatures required), first time someone stuffs votes with 20+ upvotes on their own note, entire team loses faith in anonymity system.
    • [critical/high] 1-2 Month Timeline With WebSocket, Real-Time Collaboration, and GDPR Compliance Is Fantasy (failure_modes · §scope)
      Finding-020 shows simple products take 1-3 months, real-time features add 2-3 weeks.
    • [critical/medium] Permanent Anonymity Prevents You From Moderating Harassment or Malicious Content (failure_modes · §technical_considerations)
      Technical section acknowledges 'permanent anonymity creates forensic challenge if malicious content posted.' First time someone posts 'Sarah is incompetent and should be fired' in anonymous note, you have zero recourse.

    🧭 Market skeptic

    Why care? [moderate] The pain is real (40-50% action completion, recurring themes, psychological safety barriers) but the willingness to pay is questionable.

    • Why now? [weak] The PRD provides no 'why now' argument.
    • Why win? [weak] Differentiation is Heartbeat Timeline + permanent anonymity + auto-carry actions.
    • Feature or product? [weak] This is a feature bundle that any existing retro tool could add in 4-8 weeks.

    📋 Overall

    This PRD exhibits three fatal flaws: (1) Solving symptom (low action completion) not cause (no organizational accountability culture), (2) Technical complexity (anonymous voting cryptography, WebSocket scaling, GDPR compliance) vastly underestimated relative to 1-2 month timeline, (3) Zero defensible moat against 10+ free competitors who can copy all features in 6-12 weeks.

    Critic confidence: 0.88 · Praise confidence: 0.92

    Then it adds a short cognitive-forcing diff of your answer against these findings.

    Condensed for this listing: top strengths and critical failure modes only, with detail trimmed to the first sentence. The full verdict is in examples/expected-verdict.md inside the skill.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    You already have a spec. Before you commit a sprint to it, find out whether it survives contact with reality.

    Spec Red-Team runs two reviewers that never see each other: one builds the strongest case for your spec, the other the harshest case against it. You get a real bull case and a real bear case, not one hedged "balanced" take.

    How it works

    1. Hand it a spec. A PRD, RFC, design doc or product plan, as a file path or pasted text.
    2. Commit your own take first. Before any AI output, you write down what you think works and what worries you. This stops you anchoring on the machine.
    3. Isolated review. A praise engine and a critic each see only the spec, never each other's output or your answer.
    4. Validated output. Both reviews are checked against strict schemas, so results stay structured and consistent from run to run.
    5. Verdict. You get a severity-ranked proceed / descope / kill call, plus a diff of your judgment against the AI's.

    What you get

    • Strengths worth keeping, with load-bearing ones marked 🔒 DO NOT REGRESS
    • Non-obvious good decisions the author made
    • Failure modes, scale pain, user confusion risks and engineering regrets, each rated by severity and likelihood and tied to a spec section
    • Market skeptic: Why care? Why now? Why win? Feature or product?
    • Verdict: KILL if fundamentally flawed, DESCOPE if there are critical blockers, otherwise PROCEED

    What's inside

    • SKILL.md: the review flow
    • references/: the praise engine and critic prompts
    • scripts/reckoning.mjs: a short, readable validator and renderer with no dependencies (Node 18+)
    • examples/: a real verdict

    Known limitations

    • True isolation needs an agent that can run subagents. On other agents the two reviews run one after the other, and the output says so.
    • Rendering needs Node 18+. Without it, the agent formats the output by hand.
    • Starting from a raw idea instead of a spec? Use Reckon (full flow) or Idea to PRD.

    Free and open source (MIT): github.com/alchemyguy/reckoning

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    1 install

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 1 day ago

    • Free to download with an account

    Requires

    Node.js

    Listed2 days ago

    What's inside

    Frequently Asked Questions