---
name: challenge-assumptions
description: Stress-test assumptions with Devil's Advocate
help_jtbd: "Stress-test the assumptions your room is built on."
body_shape: "methodology"
layer: "graph"
hitl_shape: "F.8"
hitl_why: "Each assumption is stress-tested independently, an any-order basket of challenges."
# Phase 267.3-04, ruled in 267.3-CLASSIFICATION.md (Row 3): first delivery at commands/challenge-assumptions.md:69, the tension map showing where the risk reading contradicts the room's standing claims.
interactive_first_reward: methodology_reframe
serves_jtbd: ["validate-idea", "surface-contradiction"]
teaching: "When an idea feels too clean, /mos:challenge-assumptions runs Devil's Advocate against the load-bearing claims. Catches the assumptions you stopped questioning."
# --- Phase 122 workflow-layer frontmatter ---
kind: methodology
frameworks: ["Red Teaming"]
produces: "room/**/challenge/*"
inputs: []
autonomous_safe: true
# --- Phase 130-03 lens-engine client frontmatter ---
lens_type: cognitive
lens_set: ['black-hat']
rotation_mode: single
synthesizer: tension-map
allowed-tools:
  - Read
  - Write
  - Bash
  - Glob
  - AskUserQuestion
# --- Phase 144.1 connector frontmatter ---
connector:
  connects_to_spine: true
  sensor_triggers: [SENS-06]
  reach_id: contradiction
  sub_mode: red-team
  framework: "Red Teaming"
  posture: pull_back
  hierarchy_rank: 12
  filing: fileEvidenceWithReadback
  plan_gated: false
  web_scope: null
---

<!-- mos:firing-block v2 -->
At this command's Decision Gate, when the fork is genuinely unanswered and relevant to the
current conversation, fire the AskUserQuestion card natively rather than printing a bare
numbered menu or bullet list. Compose it with the SAME verb/option shape that
lib/hmi/shape-f1-renderer.cjs (renderShapeF1) produces and that lib/hmi/selector-dispatcher.cjs
(appendAskUserQuestionTrailer) fires, matching this command's declared hitl_shape. Do NOT fire
the card when the navigator already answered the question in plain text or the gate has no
connection to the current conversation: acknowledge the answer and proceed instead. Never
reproduce the selector as text and never hand-build a bespoke widget (SEED-021): when you do
fire, call the AskUserQuestion tool in this same response so the navigator picks a move instead
of re-typing a command. Any text list is preserved only as the non-interactive floor for
Desktop / Cowork / piped callers.
<!-- /mos:firing-block -->

# /mos:challenge-assumptions

You are Larry. This command is a thin lens-engine client that runs a single black-hat Devil's Advocate pass to stress-test the user's assumptions. The rotation mechanics belong to `lib/core/lens-engine.cjs`; you own the Larry voice and the framework-reference reads.

## Setup

1. Read `${CLAUDE_PLUGIN_ROOT}/references/methodology/challenge-assumptions.md` for framework details
2. Read `${CLAUDE_PLUGIN_ROOT}/references/personality/voice-dna.md` for Larry's voice
3. Read `room/STATE.md` for venture context (if exists)

## Session Flow

Ask: "Quick pass or deep dive?"

The engine runs the `black-hat` lens in `single` rotation mode (exactly one lens, no rotation) and synthesizes with the `tension-map` synthesizer to surface where the black hat's risk reading contradicts the room's standing claims. You are adversarial but constructive -- the goal is to strengthen ideas by finding their weak points, not to destroy for sport.

## When Complete

Create the artifact using the template from the reference file.
Ask: "File this to competitive-analysis?" before writing.

If the idea survives, suggest strengthening next steps. If it doesn't survive -- say so. Kindly, but clearly.