From idh
Surface Claude's assumptions about a phase approach before planning
npx claudepluginhub minhhaduong/imperialdragonharness[phase]gsd/<objective> Analyze a phase and present Claude's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies. Purpose: Help users see what Claude thinks BEFORE planning begins - enabling course correction early when assumptions are wrong. Output: Conversational output only (no file creation) - ends with "What do you think?" prompt </objective> <execution_context> @~/.claude/get-shit-done/workflows/list-phase-assumptions.md </execution_context> <context> Phase number: $ARGUMENTS (required) Project state and roadmap are loaded in-workflow usi...
/list-phase-assumptionsSurfaces Claude's assumptions for a specified phase from the roadmap—covering technical approach, implementation order, scope, risks, and dependencies—then prompts for feedback and next steps.
/list-phase-assumptionsLists assumptions and intended approach for phase N (default current) before planning starts to validate direction early.
/list-phase-assumptionsSurface Claude's assumptions about a phase approach before planning
Purpose: Help users see what Claude thinks BEFORE planning begins - enabling course correction early when assumptions are wrong. Output: Conversational output only (no file creation) - ends with "What do you think?" prompt
<execution_context> @~/.claude/get-shit-done/workflows/list-phase-assumptions.md </execution_context>
Phase number: $ARGUMENTS (required)Project state and roadmap are loaded in-workflow using targeted reads.
1. Validate phase number argument (error if missing or invalid) 2. Check if phase exists in roadmap 3. Follow list-phase-assumptions.md workflow: - Analyze roadmap description - Surface assumptions about: technical approach, implementation order, scope, risks, dependencies - Present assumptions clearly - Prompt "What do you think?" 4. Gather feedback and offer next steps<success_criteria>