get-shit-done-cc 1.0.10 → 1.0.11

package/commands/gsd/help.md

@@ -55,6 +55,16 @@ Gather phase context through adaptive questioning before planning.
 
 Usage: `/gsd:discuss-phase 2`
 
+**`/gsd:research-phase <number>`**
+Comprehensive ecosystem research for niche/complex domains.
+
+- Discovers standard stack, architecture patterns, pitfalls
+- Creates RESEARCH.md with "how experts build this" knowledge
+- Use for 3D, games, audio, shaders, ML, and other specialized domains
+- Goes beyond "which library" to ecosystem knowledge
+
+Usage: `/gsd:research-phase 3`
+
 **`/gsd:list-phase-assumptions <number>`**
 Surface Claude's assumptions about a phase before planning.
 
@@ -236,6 +246,15 @@ Change anytime by editing `.planning/config.json`
 /gsd:execute-plan .planning/phases/01-foundation/01-01-PLAN.md
 ```
 
+**Building something in a niche domain (3D, games, audio, shaders):**
+
+```
+/gsd:new-project
+/gsd:research-phase 1  # Learn how experts build this
+/gsd:plan-phase 1      # Plan using research findings
+/gsd:execute-plan .planning/phases/01-foundation/01-01-PLAN.md
+```
+
 **Resuming work after a break:**
 
 ```

package/commands/gsd/research-phase.md

@@ -0,0 +1,90 @@
+---
+description: Research how to implement a phase before planning
+argument-hint: "[phase]"
+allowed-tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - Write
+  - WebFetch
+  - WebSearch
+  - mcp__context7__*
+---
+
+<objective>
+Comprehensive research on HOW to implement a phase before planning.
+
+This is for niche/complex domains where Claude's training data is sparse or outdated. Research discovers:
+- What libraries exist for this problem
+- What architecture patterns experts use
+- What the standard stack looks like
+- What problems people commonly hit
+- What NOT to hand-roll (use existing solutions)
+
+Output: RESEARCH.md with ecosystem knowledge that informs quality planning.
+</objective>
+
+<execution_context>
+@~/.claude/get-shit-done/workflows/research-phase.md
+@~/.claude/get-shit-done/templates/research.md
+@~/.claude/get-shit-done/references/research-pitfalls.md
+</execution_context>
+
+<context>
+Phase number: $ARGUMENTS (required)
+
+**Load project state:**
+@.planning/STATE.md
+
+**Load roadmap:**
+@.planning/ROADMAP.md
+
+**Load phase context if exists:**
+Check for `.planning/phases/XX-name/{phase}-CONTEXT.md` - bonus context from discuss-phase.
+</context>
+
+<process>
+1. Validate phase number argument (error if missing or invalid)
+2. Check if phase exists in roadmap - extract phase description
+3. Check if RESEARCH.md already exists (offer to update or use existing)
+4. Load CONTEXT.md if it exists (bonus context for research direction)
+5. Follow research-phase.md workflow:
+   - Analyze phase to identify knowledge gaps
+   - Determine research domains (architecture, ecosystem, patterns, pitfalls)
+   - Execute comprehensive research via Context7, official docs, WebSearch
+   - Cross-verify all findings
+   - Create RESEARCH.md with actionable ecosystem knowledge
+6. Offer next steps (plan the phase)
+</process>
+
+<when_to_use>
+**Use research-phase for:**
+- 3D graphics (Three.js, WebGL, procedural generation)
+- Game development (physics, collision, AI, procedural content)
+- Audio/music (Web Audio API, DSP, synthesis)
+- Shaders (GLSL, Metal, ISF)
+- ML/AI integration (model serving, inference, pipelines)
+- Real-time systems (WebSockets, WebRTC, sync)
+- Specialized frameworks with active ecosystems
+- Any domain where "how do experts do this" matters
+
+**Skip research-phase for:**
+- Standard web dev (auth, CRUD, REST APIs)
+- Well-known patterns (forms, validation, testing)
+- Simple integrations (Stripe, SendGrid with clear docs)
+- Commodity features Claude handles well
+</when_to_use>
+
+<success_criteria>
+- [ ] Phase validated against roadmap
+- [ ] Domain/ecosystem identified from phase description
+- [ ] Comprehensive research executed (Context7 + official docs + WebSearch)
+- [ ] All WebSearch findings cross-verified with authoritative sources
+- [ ] RESEARCH.md created with ecosystem knowledge
+- [ ] Standard stack/libraries identified
+- [ ] Architecture patterns documented
+- [ ] Common pitfalls catalogued
+- [ ] What NOT to hand-roll is clear
+- [ ] User knows next steps (plan phase)
+</success_criteria>

package/get-shit-done/references/git-integration.md

@@ -16,7 +16,7 @@ The git log should read like a changelog of what shipped, not a diary of plannin
 | BRIEF + ROADMAP created | YES     | Project initialization                |
 | PLAN.md created         | NO      | Intermediate - commit with completion |
 | RESEARCH.md created     | NO      | Intermediate                          |
-| FINDINGS.md created     | NO      | Intermediate                          |
+| DISCOVERY.md created    | NO      | Intermediate                          |
 | **Phase completed**     | YES     | Actual code shipped                   |
 | Handoff created         | YES     | WIP state preserved                   |
 
@@ -118,7 +118,7 @@ e]2f4a8 docs: initialize ecommerce-app (5 phases)
 
 - PLAN.md creation (wait for phase completion)
 - RESEARCH.md (intermediate)
-- FINDINGS.md (intermediate)
+- DISCOVERY.md (intermediate)
 - Minor planning tweaks
 - "Fixed typo in roadmap"
 

package/get-shit-done/references/plan-format.md

@@ -250,7 +250,7 @@ Use @file references to load context for the prompt:
 <context>
 @.planning/PROJECT.md           # Project vision
 @.planning/ROADMAP.md         # Phase structure
-@.planning/phases/02-auth/FINDINGS.md  # Research results
+@.planning/phases/02-auth/DISCOVERY.md  # Discovery results
 @src/lib/db.ts                # Existing database setup
 @src/types/user.ts            # Existing type definitions
 </context>

package/get-shit-done/references/scope-estimation.md

@@ -130,9 +130,9 @@ Total: 16 files, 3 plans → consistent quality
 - 02-01-PLAN.md: Setup (checkpoint: decision on auth provider)
 - 02-02-PLAN.md: Implement chosen auth solution
 
-**5. Research + implementation**
-- Research produces FINDINGS.md (separate plan)
-- Implementation consumes FINDINGS.md (separate plan)
+**5. Discovery + implementation**
+- Discovery produces DISCOVERY.md (separate plan)
+- Implementation consumes DISCOVERY.md (separate plan)
 - Clear boundary, clean handoff
 </always_split>
 

package/get-shit-done/templates/{research-prompt.md → discovery.md}

@@ -1,31 +1,39 @@
-# Research Prompt Template
+# Discovery Template
 
-For phases requiring research before planning:
+Template for `.planning/phases/XX-name/DISCOVERY.md` - shallow research for library/option decisions.
+
+**Purpose:** Answer "which library/option should we use" questions during mandatory discovery in plan-phase.
+
+For deep ecosystem research ("how do experts build this"), use `/gsd:research-phase` which produces RESEARCH.md.
+
+---
+
+## File Template
 
 ```markdown
 ---
 phase: XX-name
-type: research
-topic: [research-topic]
+type: discovery
+topic: [discovery-topic]
 ---
 
 <session_initialization>
-Before beginning research, verify today's date:
+Before beginning discovery, verify today's date:
 !`date +%Y-%m-%d`
 
 Use this date when searching for "current" or "latest" information.
 Example: If today is 2025-11-22, search for "2025" not "2024".
 </session_initialization>
 
-<research_objective>
-Research [topic] to inform [phase name] implementation.
+<discovery_objective>
+Discover [topic] to inform [phase name] implementation.
 
 Purpose: [What decision/implementation this enables]
 Scope: [Boundaries]
-Output: FINDINGS.md with structured recommendations
-</research_objective>
+Output: DISCOVERY.md with recommendation
+</discovery_objective>
 
-<research_scope>
+<discovery_scope>
 <include>
 - [Question to answer]
 - [Area to investigate]
@@ -33,12 +41,12 @@ Output: FINDINGS.md with structured recommendations
 </include>
 
 <exclude>
-- [Out of scope for this research]
+- [Out of scope for this discovery]
 - [Defer to implementation phase]
 </exclude>
-</research_scope>
+</discovery_scope>
 
-<research_protocol>
+<discovery_protocol>
 
 **Source Priority:**
 1. **Context7 MCP** - For library/framework documentation (current, authoritative)
@@ -46,7 +54,7 @@ Output: FINDINGS.md with structured recommendations
 3. **WebSearch** - For comparisons, trends, community patterns (verify all findings)
 
 **Quality Checklist:**
-Before completing research, verify:
+Before completing discovery, verify:
 - [ ] All claims have authoritative sources (Context7 or official docs)
 - [ ] Negative claims ("X is not possible") verified with official documentation
 - [ ] API syntax/configuration from Context7 or official docs (never WebSearch alone)
@@ -59,14 +67,14 @@ Before completing research, verify:
 - MEDIUM: WebSearch + Context7/official docs confirm
 - LOW: WebSearch only or training knowledge only (mark for validation)
 
-</research_protocol>
+</discovery_protocol>
 
 
 <output_structure>
-Create `.planning/phases/XX-name/FINDINGS.md`:
+Create `.planning/phases/XX-name/DISCOVERY.md`:
 
 ```markdown
-# [Topic] Research Findings
+# [Topic] Discovery
 
 ## Summary
 [2-3 paragraph executive summary - what was researched, what was found, what's recommended]
@@ -119,15 +127,20 @@ Create `.planning/phases/XX-name/FINDINGS.md`:
 </success_criteria>
 
 <guidelines>
-**When to use research prompts:**
-- Technology choice unclear
-- Best practices needed for unfamiliar domain
+**When to use discovery:**
+- Technology choice unclear (library A vs B)
+- Best practices needed for unfamiliar integration
 - API/library investigation required
-- Architecture decision pending
-- Multiple valid approaches exist
+- Single decision pending
 
 **When NOT to use:**
 - Established patterns (CRUD, auth with known library)
 - Implementation details (defer to execution)
 - Questions answerable from existing project context
+
+**When to use RESEARCH.md instead:**
+- Niche/complex domains (3D, games, audio, shaders)
+- Need ecosystem knowledge, not just library choice
+- "How do experts build this" questions
+- Use `/gsd:research-phase` for these
 </guidelines>

package/get-shit-done/templates/phase-prompt.md

@@ -32,8 +32,8 @@ Output: [What artifacts will be created]
 <context>
 @.planning/PROJECT.md
 @.planning/ROADMAP.md
-[If research exists:]
-@.planning/phases/XX-name/FINDINGS.md
+[If discovery exists:]
+@.planning/phases/XX-name/DISCOVERY.md
 [Relevant source files:]
 @src/path/to/relevant.ts
 </context>