devils-advocatelisted

# devils-advocate Sharp self-review critique. Two modes: `pre-share` stress-tests docs before sharing; `pre-launch` runs forward-looking failure analysis before committing resources. --- ## Mode: pre-share (default) Stress-test your thinking before you share a doc. Use for PRDs, strategy docs, customer outreach, board updates, decision memos. ### THINK Before critiquing, understand what the doc is actually trying to achieve. Don't critique a strategy doc for lacking implementation detail, or a customer email for lacking financial projections. Ask the user 2-3 questions: 1. What's the one thing you need the reader to do or decide after reading this? 2. What's the part you're least confident about? 3. Who's the hardest person in the audience to convince? These answers calibrate the critique. If the goal is "get the CEO to approve budget," the critique focuses on the business case and risk. If the goal is "get engineering to estimate," the critique focuses on clarity and scope. --- ## DECIDE Choose the critique lens based on doc type: | Doc type | Critique lens | |---|---| | PRD / product brief | Are the problem and solution clearly separated? Is the evidence for the problem strong enough to justify the solution? Are non-goals explicit? | | Strategy doc | Are the bets clear? Is the "not doing" list honest? Are the assumptions about the market testable? | | Customer outreach | Does it lead with the customer's problem or our product? Is the ask clear? Could it be misin