3e8e5d537d
Show slash commands inline so users can copy them to fresh context, matching pattern used by other GSD commands. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
58 lines
2.0 KiB
Markdown
58 lines
2.0 KiB
Markdown
---
|
|
description: Gather phase context through adaptive questioning before planning
|
|
argument-hint: "[phase]"
|
|
---
|
|
|
|
<objective>
|
|
Help the user articulate their vision for a phase through collaborative thinking.
|
|
|
|
Purpose: Understand HOW the user imagines this phase working — what it looks like, what's essential, what's out of scope. You're a thinking partner helping them crystallize their vision, not an interviewer gathering technical requirements.
|
|
|
|
Output: {phase}-CONTEXT.md capturing the user's vision for the phase
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/get-shit-done/workflows/discuss-phase.md
|
|
@~/.claude/get-shit-done/templates/context.md
|
|
</execution_context>
|
|
|
|
<context>
|
|
Phase number: $ARGUMENTS (required)
|
|
|
|
**Load project state first:**
|
|
@.planning/STATE.md
|
|
|
|
**Load roadmap:**
|
|
@.planning/ROADMAP.md
|
|
</context>
|
|
|
|
<process>
|
|
1. Validate phase number argument (error if missing or invalid)
|
|
2. Check if phase exists in roadmap
|
|
3. Check if CONTEXT.md already exists (offer to update if yes)
|
|
4. Follow discuss-phase.md workflow:
|
|
- Present phase from roadmap
|
|
- Ask: "How do you imagine this working?"
|
|
- Follow their thread — dig into what excites them
|
|
- Sharpen the core — what's essential for THIS phase
|
|
- Find boundaries — what's explicitly out of scope
|
|
- Present decision gate (ready / ask more / let me add context)
|
|
- Create CONTEXT.md capturing their vision
|
|
5. Offer next steps (research or plan the phase)
|
|
|
|
CRITICAL — User is the visionary, you are the builder:
|
|
- Ask about vision, feel, essential outcomes
|
|
- DON'T ask about technical risks (you figure those out)
|
|
- DON'T ask about codebase patterns (you read the code)
|
|
- DON'T ask about success metrics (too corporate)
|
|
- DON'T interrogate about constraints they didn't mention
|
|
</process>
|
|
|
|
<success_criteria>
|
|
|
|
- Phase validated against roadmap
|
|
- Vision gathered through collaborative thinking (not interrogation)
|
|
- CONTEXT.md captures: how it works, what's essential, what's out of scope
|
|
- User knows next steps (research or plan the phase)
|
|
</success_criteria>
|