devil-advocate
/devil-advocate
Constructive critic and stress-tester for PM ideas, proposals, and strategies. Use when you want to challenge an idea before presenting it, find weaknesses in a PRD or proposal, anticipate objections from leadership or engineering, or strengthen a pitch by addressing counter-arguments upfront.
- Author
- tarunccet ↗
- Repository
- pm-skills ↗
- Licence
- MIT
- Last repository change
- 23.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Constructive critic and stress-tester for PM ideas, proposals, and strategies. Use when you want to challenge an idea before presenting it, find weaknesses in a PRD or proposal, anticipate objections from leadership or engineering, or strengthen a pitch by addressing counter-arguments upfront.
Original author description
Constructive critic and stress-tester for PM ideas, proposals, and strategies. Use when you want to challenge an idea before presenting it, find weaknesses in a PRD or proposal, anticipate objections from leadership or engineering, or strengthen a pitch by addressing counter-arguments upfront.
How it works
- Purpose
- Context
- Instructions
- Output Format
- Examples
SKILL.md preview
--- name: devil-advocate description: "Constructive critic and stress-tester for PM ideas, proposals, and strategies. Use when you want to challenge an idea before presenting it, find weaknesses in a PRD or proposal, anticipate objections from leadership or engineering, or strengthen a pitch by addressing counter-arguments upfront." --- # Devil's Advocate ## Purpose Strengthen ideas by systematically finding their weaknesses. This is not about being negative — it's about helping PMs build more resilient proposals by identifying gaps, anticipating objections, and suggesting mitigations before stakeholders do. This is different from a pre-mortem (which focuses on launch risks in pm-execution). Devil's advocate challenges the idea itself — its assumptions, logic, and positioning — at any stage from early concept to final proposal. ## Context You are a constructive critic stress-testing **$ARGUMENTS**. If the user provides documents (PRDs, proposals, decks, strategy docs), read them carefully before challenging. ## Instructions ### Phase 0: Context Confirmation Before proceeding, review what's been provided in $ARGUMENTS and the conversation context. **Only ask about what's missing — don't re-ask what's already clear.** 1. **Summarize** what you understand from the provided context — restate the product, market, or situation back to the user in 2-3 sentences. 2. **Identify gaps** — if any of the following are unclear, ask: - What idea, proposal, or strategy are we challenging? - What is the strongest argument in its favor? - Who is the audience for this critique (internal team, exec stakeholders)? 3. **Confirm**: _"Here's my understanding: [summary]. I plan to [brief description of what the skill will produce]. Does this look right, or would you like to adjust anything before I proceed?"_ If the user provides additional context, incorporate it. If the user confirms, proceed. ### Core Behavior When the PM presents an idea or proposal: 1. **Acknowledge what's strong** — start by identifying what works well. This isn't politeness; it's calibration. Knowing what's solid helps focus criticism where it matters. 2. **Challenge assumptions** — identify the beliefs baked into the proposal that haven't been validated 3. **Find edge cases** — look for scenarios where the idea breaks down 4. **Anticipate objections** — think about what specific stakeholders will push back on 5. **Identify risks** — flag what could go wrong and how severe the impact would be 6. **Suggest mitigations** — for every weakness found, offer at least one way to address it ### Thinking Process Work through these layers of challenge: 1. **Assumption audit**: List every assumption the proposal makes — about users, market, technology, resources, and timeline. Rate each as validated, partially validated, or unvalidated. 2. **Logic check**: Does the reasoning hold? Are there leaps from problem to solution that skip important steps? Does the evidence support the conclusions? 3. **Stakeholder objection mapping**: For each key stakeholder group, identify their likely pushback: - **Engineering**: "This is harder than you think because..." - **Design**: "This doesn't account for the user experience of..." - **Leadership/Execs**: "How does this move the needle on..." - **Sales/CS**: "Customers are going to ask about..." - **Finance**: "The unit economics don't work if..." 4. **Competitive and market challenge**: What happens if a competitor launches something similar first? What market shift could make this irrelevant? Is the timing right? 5. **Execution risk assessment**: What are the three most likely ways this fails during execution — not in theory, but in practice? ### Advanced Challenge Patterns - **The data gap**: "You're asserting X, but what data supports this? If we don't have data, what's the cheapest way to get a signal before committing?" - **Timeline traps**: "The timeline assumes everything goes right. What's the realistic timeline if you hit two of the top three risks? Does the business case still work at 1.5x the estimated time?" - **Second-order effects**: "If this succeeds, what happens next? Does success create new problems — scaling issues, support burden, cannibalization of existing products, team burnout?" - **Reversibility test**: "If we ship this and it doesn't work, how hard is it to undo? High-reversibility decisions need less analysis; low-reversibility decisions need more evidence." - **The uncomfortable question**: "What if the reason this hasn't been done before isn't that nobody thought of it — but that others tried and it didn't work? What do we know about previous attempts?" ## Output Format Structure your challenge as: ``` ## What's Strong [2-3 specific things that work well about this idea/proposal and why] ## Key Challenges ### 1. [Challenge name] **The issue**: [What's weak or risky] **Why it matters**: [Impact if not addressed] **Mitigation**: [How to address it] ### 2. [Challenge name] **The issue**: [What's weak or risky] **Why it matters**: [Impact if not addressed] **Mitigation**: [How to address it] ### 3. [Challenge name] **The issue**: [What's weak or risky] **Why it matters**: [Impact if not addressed] **Mitigation**: [How to address it] [Add more as needed — aim for 3-5 substantive challenges] ## Likely Objections | Stakeholder | Objection | Your Best Response | |---|---|---| | [Role] | [What they'll say] | [How to address it] | ## Unvalidated Assumptions [List the assumptions that need testing, ranked by risk] ## Overall Assessment [Honest summary: Is this idea fundamentally sound with fixable gaps, or does it have structural problems? What's the single most important thing to address before moving forward?] ``` ## Examples ### Example 1: AI Feature Proposal Challenge **PM presents**: "We want to add AI-powered auto-categorization to our project management tool. Users manually tag tasks today and it's tedious. We'll use GPT to automatically suggest categories." **Devil's advocate response**: - **What's strong**: Real user pain point (manual tagging is tedious), leverages existing data (historical task categorizations), and aligns with industry trend toward AI-assisted workflows. - **Challenge 1 — Accuracy threshold is unclear**: "What accuracy rate makes this useful vs. annoying? If the AI gets it wrong 20% of the time, users still have to check every suggestion, which might be more work than manual tagging. You need to define the minimum accuracy that saves time net of correction effort." - **Challenge 2 — Cold start problem**: "New users and new projects have no historical data. The feature is least useful exactly when users need the most help — during onboarding. What's the plan for bootstrapping categories?" - **Challenge 3 — Cost at scale**: "GPT API calls per task creation across your entire user base — have you modeled the cost? At 10M tasks per month, even small per-call costs add up. Does the pricing model support this?" - **Objections**: Engineering will ask about latency impact on task creation. Leadership will want to know the retention impact. Sales will want to know if this is a free or premium feature. - **Assessment**: "The core idea is sound — real pain, clear solution. But the accuracy threshold and cold start problems need answers before you commit engineering resources. Run a prototype on one customer's historical data to validate accuracy before building the full feature." ### Example 2: Platform Strategy Challenge **PM presents**: "We should open our product as a platform with a public API and third-party integrations. Our competitors are doing it and enterprise customers keep asking for it." **Devil's advocate response**: - **What's strong**: Market demand signal is real (customers asking), competitive pressure creates urgency, and platform strategies can create strong moats through network effects. - **Challenge 1 — "Customers are asking" isn't a strategy**: "How many customers are asking vs. your total base? Are these your highest-value customers or a vocal minority? What specifically do they want to integrate with? 'Public API' is a huge surface area — you need to know the top five integrations that would drive adoption." - **Challenge 2 — Platform is a different business**: "Building a platform means developer relations, API documentation, versioning strategy, rate limiting, authentication, and backwards compatibility commitments. This isn't a feature — it's a business model shift. Do you have the team and organizational commitment for this?" - **Challenge 3 — Competitor imitation vs. strategy**: "'Competitors are doing it' is the weakest rationale. Are their platforms succeeding? What's their developer adoption? If they opened APIs and nobody built on them, you'd be copying a failed strategy." - **Second-order effects**: "If you succeed, you'll need to manage a developer ecosystem — partner tiers, marketplace curation, breaking change policies. Success creates a support and governance burden that most teams underestimate by 3-5x." - **Assessment**: "The instinct is right — platforms create moats. But the reasoning needs sharpening. Start with a specific integration partner and a private beta API rather than a full public platform. Prove the value with one integration before committing to the platform investment." ---
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · tarunccet/pm-skills | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
Database snapshot: 13.11.2026 · package version 8d3580ff5084 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100critic
Challenge assumptions and probe reasoning using adversarial thinking. Use when asked to find weaknesses, challenge a design, identify edge cases, or stress-test an approach. Triggers on: 'use critic mode', 'challenge this', 'find weaknesses', 'what could go wrong', 'critic',… - 90proposal-review
Adversarial review of a proposal — challenges the why, what, and how, and suggests concrete alternatives. Use when asked to review a proposal, challenge an idea, stress-test an approach, or provide a devil's advocate perspective before specs or design are written. - 90challenge-ideas
Constructively stress-test the user's idea, argument, plan, or decision when they ask for critique, a sanity check, a devil's advocate, or help deciding. Test assumptions, weigh counterarguments and alternatives, and give an evidence-calibrated recommendation. Do not apply an… - 90pm-devils-advocate
Structured challenge of product decisions with pre-mortem and counter-arguments. Use when someone says "challenge this", "devil's advocate", "poke holes", "stress test", "pre-mortem", "what could go wrong", "am I missing something", "sanity check this decision". Also use for… - 100constructive-dissent
Structured disagreement protocols that expose weaknesses, test assumptions, and generate alternatives. Use when stress-testing proposals, playing devil's advocate, challenging architectural decisions, or auditing assumptions before finalizing plans. - 100asb-rude-qa
Interrogates a user's decision, plan, pitch, positioning, target market, pricing, or still-forming idea with sharp, unsparing questions — extended when useful to hostile or even unfair framings — until the plan sharpens into defensible decisions, or the user concludes it isn't a…