kai/claude-config
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
2876cca8fe7b3e8c2d62a3870aa62530c5e42e02
claude-config/commands/gsd/list-phase-assumptions.md
Yaojia Wang 2876cca8fe chore: initial backup of Claude Code configuration 
Includes: CLAUDE.md, settings.json, agents, commands, rules, skills,
hooks, contexts, evals, get-shit-done, plugin configs (installed list
and marketplace sources). Excludes credentials, runtime caches,
telemetry, session data, and plugin binary cache.
2026-03-24 22:26:05 +01:00

1.4 KiB
Raw Blame History

name, description, argument-hint, allowed-tools
name description argument-hint allowed-tools
gsd:list-phase-assumptions Surface Claude's assumptions about a phase approach before planning [phase]
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

<execution_context> @C:/Users/yaoji/.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>

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