git:20260426.d53cc6c to git:20260914.e75f220

1 added, 1 removed. Audit A to A.

---

name: gsd-list-phase-assumptions

- description: "Surface Claude's assumptions about a phase approach before planning"

+ description: "Use when the user wants to see what the agent assumes about a phase's approach, order, scope, risks and dependencies before planning starts, instead of running a full discuss session. Read-only; ends with a prompt for feedback."

argument-hint: "[phase]"

allowed-tools:

- Read

- Bash

- Grep

- Glob

---

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>

@$HOME/.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.

</context>

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

</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>