dobrinz123/claude-skills-share/gsd-list-phase-assumptions

<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 using targeted reads. </context>

<process>

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?"

1. Gather feedback and offer next steps

</process>

<success_criteria>

• Phase validated against roadmap
• Assumptions surfaced across five areas
• User prompted for feedback
• User knows next steps (discuss context, plan phase, or correct assumptions)

</success_criteria>