mcpField
G
gsd-list-phase-assumptions

gsd-list-phase-assumptions

github.com/shoootyouAgent workflows22109 installsUpdated 32w ago
Repository

About gsd-list-phase-assumptions

gsd-list-phase-assumptions analyzes a roadmap phase and presents Claude's assumptions about its approach, order, scope, risks, and dependencies. It is for users who want to correct misunderstandings before planning; the output is conversational and creates no files.

Key features

  1. 01Validates the phase number
  2. 02Checks the roadmap for the phase
  3. 03Surfaces assumptions across five areas
  4. 04Prompts for feedback and next steps

Use cases

  1. 01Correct technical assumptions before planning
  2. 02Discuss a phase's risks and dependencies

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/shoootyou/get-shit-done-multi --skill gsd-list-phase-assumptions

After installing, type/gsd-list-phase-assumptionsin Claude Code to confirm it loaded.

Details

From the project README
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> @{{PLATFORM_ROOT}}/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>

Comments

Markdown supported