Claude-skill-registry constructive-dissent
Structured disagreement protocols to strengthen proposals through systematic challenge and alternative generation.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/constructive-dissent" ~/.claude/skills/majiayu000-claude-skill-registry-constructive-dissent && rm -rf "$T"
manifest:
skills/data/constructive-dissent/SKILL.mdtags
source content
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
- Explicit assumptions: What's stated as given?
- Implicit assumptions: What's unstated but operating?
- Structural assumptions: What framework biases exist?
- 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
- Goal abstraction: Extract core objectives from specific implementation
- Constraint relaxation: Temporarily remove limitations
- Method inversion: Consider opposite approaches
- Cross-domain inspiration: Apply solutions from other fields
- 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
## 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