strategy-critical-reasoning

Apply five structured reasoning modes to stress-test strategies and proposals.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/scanady/nexus-agents --skill strategy-critical-reasoning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategy-critical-reasoning
Source: https://github.com/scanady/nexus-agents/tree/main/skills/strategy-critical-reasoning
Command: npx skills add https://github.com/scanady/nexus-agents --skill strategy-critical-reasoning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Challenges ideas, plans, decisions, and proposals by applying 5 structured reasoning modes to stress-test before commitment.

Core Features & Use Cases

  • Five structured reasoning modes: Expose My Assumptions, Argue the Other Side, Find the Failure Modes, Attack This, Test the Evidence, each with guided references and workflow.
  • Workflow-driven critique: steelman the thesis first, present strongest counter-arguments, surface weaknesses, and synthesize a strengthened position with trade-offs.
  • Use cases include pre-mortems, red-teaming, evidence audits, and devil's-advocate reviews to reduce risk and improve decision quality.

Quick Start

Provide a strategy and say 'stress test this' to begin a mode-driven critique.

Frequently Asked Questions about strategy-critical-reasoning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test a business strategy before committing to it?

Stress-testing a product proposal involves applying structured reasoning modes like pre-mortems and evidence audits to challenge assumptions, present counter-arguments, and produce a structured evaluation of risks before commitment.

What is the best way to run a pre-mortem analysis on a product proposal?

Running a pre-mortem analysis uses mode-specific workflows to find failure modes, attack the thesis, and test the evidence, ultimately yielding a structured evaluation that highlights weaknesses and improves decision quality.

How do I red-team an architecture decision to find hidden weaknesses?

Red-teaming an architecture decision involves arguing the other side and attacking the proposal using adversarial thinking workflows, which exposes hidden assumptions and generates a comprehensive risk analysis.

Can I use this approach for early-stage decisions or only fully developed plans?

This approach works for early-stage decisions, product strategies, architectures, and business plans. It scrutinizes risks and assumptions at any development stage where a strategy or proposal requires structured critique.

What are the limitations of using adversarial thinking for risk analysis?

A limitation of adversarial thinking for risk analysis is that while it effectively attacks a proposal and argues the other side, the process requires a clearly defined initial strategy to steelman and evaluate before generating trade-offs.