home / skills / nickcrew / claude-cortex / constructive-dissent

constructive-dissent skill

/skills/constructive-dissent

This skill systematically challenges proposals using structured dissent protocols to expose weaknesses and generate superior alternatives.

npx playbooks add skill nickcrew/claude-cortex --skill constructive-dissent

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
5.7 KB
---
name: constructive-dissent
description: Structured disagreement protocols to strengthen proposals through systematic challenge and alternative generation.
keywords:
  - critique
  - challenge
  - alternatives
  - devil's advocate
  - assumption testing
triggers:
  - challenge this
  - devil's advocate
  - what could go wrong
  - stress test
  - critique proposal
  - question assumptions
---

# Constructive Dissent Skill

Systematically challenge proposals through structured dissent protocols that expose weaknesses, test assumptions, and generate superior alternatives.

## When to Use This Skill

- Before finalizing major decisions
- Testing proposals for weaknesses
- Generating alternative approaches
- Assumption auditing
- Stress-testing architectural decisions
- Evaluating competing solutions

## Dissent Intensity Framework

### Gentle Level (Refinement-focused)

**Purpose**: Improve without fundamental challenge to core approach

**Challenge Characteristics**:
- Assumption questioning with evidence requests
- Edge case identification with boundary testing
- Implementation detail refinement
- Risk mitigation suggestions
- Alternative approach comparison

**Example Phrases**:
- "This approach has merit, but what if we considered..."
- "I'm curious about how this would handle..."
- "What assumptions are we making about..."
- "Have we considered the implications of..."

### Systematic Level (Methodology-challenging)

**Purpose**: Challenge underlying methods while respecting intent

**Challenge Characteristics**:
- Methodology critique with alternatives
- Evidence evaluation with validation requirements
- Stakeholder perspective integration
- Long-term consequence analysis
- Resource allocation questioning

**Example Phrases**:
- "While the goal is sound, I question whether this methodology..."
- "The evidence presented doesn't address..."
- "From the perspective of [stakeholder], this might..."
- "Long-term, this could lead to..."

### Rigorous Level (Premise-challenging)

**Purpose**: Attack fundamental premises, demand comprehensive justification

**Challenge Characteristics**:
- Fundamental premise questioning
- Paradigm alternative generation
- Success criteria challenge
- Stakeholder priority reordering
- Innovation opportunity identification

**Example Phrases**:
- "I fundamentally question whether we're solving the right problem..."
- "This entire framework assumes X, but what if..."
- "Are we defining success correctly, or should we..."
- "This prioritizes X, but shouldn't we prioritize Y because..."

### Paradigmatic Level (Worldview-challenging)

**Purpose**: Question fundamental worldview, propose radical alternatives

**Challenge Characteristics**:
- Worldview assumption identification
- Revolutionary approach generation
- Value system questioning
- Future-state visioning
- Breakthrough innovation pursuit

**Example Phrases**:
- "This assumes a world where X, but we're moving toward..."
- "What if everything we think we know about this is wrong?"
- "Instead of optimizing within constraints, what if we eliminated them?"
- "Are we thinking big enough?"

## Challenge Methodologies

### Assumption Audit

1. **Explicit assumptions**: What's stated as given?
2. **Implicit assumptions**: What's unstated but operating?
3. **Structural assumptions**: What framework biases exist?
4. **Temporal assumptions**: What time constraints are artificial?

### Edge Case Generation

- **Scale extremes**: Minimum and maximum scenarios
- **Performance limits**: Where does it break?
- **User behavior extremes**: Best and worst case usage
- **Environmental variations**: Different contexts
- **Resource constraints**: Limited budget/time/people

### Alternative Generation Framework

1. **Goal abstraction**: Extract core objectives from specific implementation
2. **Constraint relaxation**: Temporarily remove limitations
3. **Method inversion**: Consider opposite approaches
4. **Cross-domain inspiration**: Apply solutions from other fields
5. **Future projection**: Design for different conditions

### Stakeholder Advocacy

- **End user**: How does this affect people using it?
- **Maintainer**: What's the ongoing cost?
- **Security**: What risks does this introduce?
- **Accessibility**: Who might be excluded?
- **Future stakeholder**: Who isn't here yet?

## Output Template

```markdown
## Constructive Dissent Analysis: [Proposal Title]

### Intensity Level: [Selected Level]

### Executive Summary
[2-3 sentence summary of key challenges and recommendations]

### Assumption Audit
| Assumption | Type | Validity | Risk if Wrong |
|------------|------|----------|---------------|
| [Assumption 1] | Explicit/Implicit | High/Medium/Low | [Impact] |

### Challenges Raised

#### Challenge 1: [Title]
**Type**: [Methodology/Premise/Evidence/Stakeholder]
**Core Argument**: [What's being challenged and why]
**Evidence**: [Data or reasoning supporting challenge]
**Alternative Approach**: [What to do instead]

### Generated Alternatives

#### Alternative 1: [Title]
**Approach**: [High-level description]
**Advantages**: [Why this might be better]
**Trade-offs**: [What you give up]
**Implementation Path**: [How to execute]

### Synthesis Recommendations

#### Strengthen Current Proposal
1. [Specific improvement]
2. [Specific improvement]

#### Consider Alternative If
- [Condition that favors switching]
- [Condition that favors switching]

### Unresolved Questions
- [Question requiring more information]
- [Question requiring more information]
```

## Success Indicators

- Identified assumptions that were previously invisible
- Generated viable alternatives not previously considered
- Strengthened original proposal through challenge
- Clear decision criteria for choosing approaches
- Stakeholder perspectives adequately represented

Overview

This skill provides structured dissent protocols to systematically challenge proposals, expose hidden weaknesses, and generate better alternatives. It codifies intensity levels from gentle refinement to paradigmatic upheaval and supplies reproducible methods like assumption audits, edge-case generation, and alternative framing. Use it to strengthen decisions, stress-test designs, and surface new options before committing resources.

How this skill works

The skill inspects a proposal by applying a chosen dissent intensity and a set of challenge methodologies. It runs an assumption audit, generates edge cases, critiques methodology and evidence, and produces alternative approaches with trade-offs and implementation paths. Outputs follow a compact template: executive summary, assumption table, concrete challenges, generated alternatives, synthesis recommendations, and unresolved questions.

When to use it

  • Before finalizing major product, architecture, or strategy decisions
  • When testing proposals for hidden assumptions and failure modes
  • To generate alternative approaches and compare trade-offs
  • During stakeholder reviews to surface diverse perspectives
  • When auditing long-term consequences or resource allocations

Best practices

  • Select an intensity level that matches risk tolerance and stage of planning
  • Document explicit, implicit, structural, and temporal assumptions early
  • Combine edge-case generation with stakeholder advocacy for balanced critique
  • Produce at least two viable alternatives and list clear trade-offs
  • Keep challenges evidence-focused and actionable, not personal

Example use cases

  • Refining a proposed microservice architecture before implementation
  • Stress-testing a business case by simulating worst-case financial scenarios
  • Auditing product requirements to uncover inaccessible user flows
  • Comparing competing vendor solutions with structured trade-off analysis
  • Reframing a roadmap item by inverting assumptions to find disruptive options

FAQ

How do I choose a dissent intensity?

Match intensity to decision impact: use Gentle for refinement, Systematic for methodology critique, Rigorous for premise reassessment, and Paradigmatic when exploring radical alternatives.

Can this be used in time-constrained reviews?

Yes. Focus on a short assumption audit and 1–2 high-impact edge cases to get meaningful results quickly.