Benchmark Due Diligence
Run adversarial due-diligence on a competitor or role-model you envy, separating marketing bubble from real signal and mapping their validated playbook onto your own resources.
That founder, product, or creator whose success looks suspiciously shiny — how much is real, how much is luck, and what can you actually copy? This playbook tears it down and ends at "what this means for me."
Who it's for: founders, marketers, strategists, indie hackers, investors
Example
"Tear down how this #1 Product Hunt launch actually happened" → A teardown splitting real method from hype, with a replicable playbook adapted to your resources
CLAUDE.md Template
New here? 3-minute setup guide → | Already set up? Copy the template below.
npx ccplaybooks add benchmark-due-diligence# Benchmark Due Diligence
Take a benchmark the user envies — a founder, KOL, company, or product whose success looks suspiciously shiny — and produce a teardown that ends in **"what this means for ME"**, not a neutral report. The deliverable answers three questions a balanced briefing never does: *How much of this success is real vs marketing bubble? How much is replicable method vs luck/timing? And what, specifically, can the commissioner do with it?*
This is the adversarial, decision-oriented cousin of `deep-research`. Where deep-research builds a trustworthy picture of the world, this skill **assumes the picture is inflated until proven otherwise** and converts the survivors into the commissioner's own moves.
## CRITICAL: run inline, never `context: fork`
This skill is an **orchestrator** — it spawns parallel collection + verification agents (via the `Workflow` tool, or `Task` agents) and may invoke other skills (`deep-research`, `osint-investigate`, `qcc`). Subagents cannot spawn subagents or call skills. Setting `context: fork` would silently break the entire fan-out. **Do not add a `context` field.** (Same constraint osint-investigate documents — it's a hard runtime rule, not a preference.)
## The one rule that protects the commissioner: two injection channels
Get new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Run adversarial due-diligence on a competitor or role-model you envy, separating marketing bubble from real signal and mapping their validated playbook onto your own resources.
What's Inside
The template covers:
- CRITICAL: run inline, never
context: fork - The one rule that protects the commissioner: two injection channels
- Phase 0 — nail the foundation by evidence, not appearance (do this BEFORE any agent)
- The four-phase orchestration
- Don't rebuild what already exists
- Read before you run
Quick Start
Step 1: Create a Project Folder
Make a dedicated folder for this workflow and open it in Claude Code.
Step 2: Download the Template
Click Download above to save the template, then drop it into your project as CLAUDE.md (or paste it into your existing one).
Step 3: Start Working
Tell Claude what you need in plain language — it will follow the template's workflow automatically. For example:
Tear down how this #1 Product Hunt launch actually happened
Claude reads the template and runs the steps for you.