Files
get-shit-done/commands/gsd/list-phase-assumptions.md
Tim Willis 4d92b3cdda feat: add Claude Code marketplace plugin support
Add complete marketplace plugin configuration and documentation for GSD,
enabling installation via Claude Code's plugin marketplace.

Changes:
- Add .claude-plugin/marketplace.json and plugin.json manifests
- Add marketplace installation instructions to README.md
- Update all command files with marketplace tool permissions
- Add plugin conversion design and implementation documentation
- Update .gitignore for Claude Code plugin artifacts

Users can now install via:
  /plugin marketplace add glittercowboy/get-shit-done
  /plugin install get-shit-done@get-shit-done
2026-01-06 18:11:30 -06:00

1.4 KiB

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> @~/.claude/get-shit-done/workflows/list-phase-assumptions.md </execution_context>

Phase number: $ARGUMENTS (required)

Load project state first: @.planning/STATE.md

Load roadmap: @.planning/ROADMAP.md

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>