ItsSalvatore/gsd-list-phase-assumptions

<cursor_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-list-phase-assumptions or describes a task matching this skill.
• Treat all user text after the skill mention as {{GSD_ARGS}}.
• If no arguments are present, treat {{GSD_ARGS}} as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

• Present options as a numbered list in your response text
• Ask the user to reply with their choice
• For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Cursor tools when executing GSD workflows:

• Shell for running commands (terminal operations)
• StrReplace for editing existing files
• Read, Write, Glob, Grep, Task, WebSearch, WebFetch, TodoWrite as needed

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use Task(subagent_type="generalPurpose", ...)
• The model parameter maps to Cursor's model options (e.g., "fast") </cursor_skill_adapter>

<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> @C:/Users/mano/Desktop/PKHEX!/.cursor/get-shit-done/workflows/list-phase-assumptions.md </execution_context>

<context> Phase number: {{GSD_ARGS}} (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?" 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>