feat: add research-project command for pre-roadmap ecosystem research
Adds /gsd:research-project to research domain ecosystem before creating roadmap. Spawns parallel agents to investigate stack, features, architecture, and pitfalls. New files: - commands/gsd/research-project.md - get-shit-done/workflows/research-project.md - get-shit-done/templates/research-project/ (5 templates) Modified: - new-project.md: offers research vs direct roadmap options - create-roadmap.md: loads research if exists - workflows/create-roadmap.md: uses research to inform phases Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -24,6 +24,7 @@ Roadmaps define what work happens in what order. Run after /gsd:new-project.
|
||||
<context>
|
||||
@.planning/PROJECT.md
|
||||
@.planning/config.json
|
||||
@.planning/research/SUMMARY.md (if exists)
|
||||
</context>
|
||||
|
||||
<process>
|
||||
|
||||
@@ -303,7 +303,15 @@ Project initialized:
|
||||
|
||||
## ▶ Next Up
|
||||
|
||||
**[Project Name]** — create roadmap
|
||||
Choose your path:
|
||||
|
||||
**Option A: Research first** (recommended for new domains)
|
||||
Research the ecosystem before creating roadmap. Discovers standard stacks, expected features, architecture patterns, and common pitfalls.
|
||||
|
||||
`/gsd:research-project`
|
||||
|
||||
**Option B: Create roadmap directly** (for familiar domains)
|
||||
Skip research if you know this domain well or have a clear spec.
|
||||
|
||||
`/gsd:create-roadmap`
|
||||
|
||||
|
||||
134
commands/gsd/research-project.md
Normal file
134
commands/gsd/research-project.md
Normal file
@@ -0,0 +1,134 @@
|
||||
---
|
||||
name: gsd:research-project
|
||||
description: Research domain ecosystem before creating roadmap
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Write
|
||||
- Bash
|
||||
- Glob
|
||||
- Grep
|
||||
- Task
|
||||
- WebFetch
|
||||
- WebSearch
|
||||
- mcp__context7__*
|
||||
---
|
||||
|
||||
<objective>
|
||||
Comprehensive domain research before roadmap creation.
|
||||
|
||||
Answers the questions that inform quality roadmaps:
|
||||
- What's the standard stack for this type of product?
|
||||
- What features do users expect?
|
||||
- How are these systems typically structured?
|
||||
- What do projects in this domain commonly get wrong?
|
||||
|
||||
Run after `/gsd:new-project`, before `/gsd:create-roadmap`.
|
||||
|
||||
Output: `.planning/research/` folder with ecosystem knowledge.
|
||||
</objective>
|
||||
|
||||
<execution_context>
|
||||
@~/.claude/get-shit-done/workflows/research-project.md
|
||||
@~/.claude/get-shit-done/templates/research-project/SUMMARY.md
|
||||
@~/.claude/get-shit-done/templates/research-project/STACK.md
|
||||
@~/.claude/get-shit-done/templates/research-project/FEATURES.md
|
||||
@~/.claude/get-shit-done/templates/research-project/ARCHITECTURE.md
|
||||
@~/.claude/get-shit-done/templates/research-project/PITFALLS.md
|
||||
</execution_context>
|
||||
|
||||
<context>
|
||||
@.planning/PROJECT.md
|
||||
@.planning/config.json (if exists)
|
||||
</context>
|
||||
|
||||
<process>
|
||||
|
||||
<step name="validate">
|
||||
```bash
|
||||
# Verify project exists
|
||||
[ -f .planning/PROJECT.md ] || { echo "ERROR: No PROJECT.md found. Run /gsd:new-project first."; exit 1; }
|
||||
|
||||
# Check if roadmap already exists
|
||||
[ -f .planning/ROADMAP.md ] && echo "WARNING: ROADMAP.md already exists. Research is typically done before roadmap creation."
|
||||
|
||||
# Check if research already exists
|
||||
[ -d .planning/research ] && echo "RESEARCH_EXISTS" || echo "NO_RESEARCH"
|
||||
```
|
||||
</step>
|
||||
|
||||
<step name="check_existing">
|
||||
**If RESEARCH_EXISTS:**
|
||||
|
||||
Use AskUserQuestion:
|
||||
- header: "Research exists"
|
||||
- question: "Research folder already exists. What would you like to do?"
|
||||
- options:
|
||||
- "View existing" — Show current research summary
|
||||
- "Replace" — Run fresh research (will overwrite)
|
||||
- "Cancel" — Keep existing research
|
||||
|
||||
If "View existing": Read and display `.planning/research/SUMMARY.md`, then exit
|
||||
If "Cancel": Exit
|
||||
If "Replace": Continue with workflow
|
||||
</step>
|
||||
|
||||
<step name="execute_research">
|
||||
Follow the research-project.md workflow:
|
||||
- Analyze PROJECT.md to determine domain
|
||||
- Identify research questions based on domain
|
||||
- Spawn parallel research agents
|
||||
- Aggregate results into `.planning/research/`
|
||||
- Create SUMMARY.md with roadmap implications
|
||||
</step>
|
||||
|
||||
<step name="done">
|
||||
```
|
||||
Research complete:
|
||||
|
||||
- Summary: .planning/research/SUMMARY.md
|
||||
- Stack: .planning/research/STACK.md
|
||||
- Features: .planning/research/FEATURES.md
|
||||
- Architecture: .planning/research/ARCHITECTURE.md
|
||||
- Pitfalls: .planning/research/PITFALLS.md
|
||||
|
||||
---
|
||||
|
||||
## ▶ Next Up
|
||||
|
||||
**Create roadmap** — informed by research
|
||||
|
||||
`/gsd:create-roadmap`
|
||||
|
||||
<sub>`/clear` first → fresh context window</sub>
|
||||
|
||||
---
|
||||
```
|
||||
</step>
|
||||
|
||||
</process>
|
||||
|
||||
<when_to_use>
|
||||
**Use research-project for:**
|
||||
- Greenfield projects in established domains (community, e-commerce, SaaS)
|
||||
- When "what features should exist" is partially unknown
|
||||
- Complex integrations requiring ecosystem knowledge
|
||||
- Domains where best practices matter (auth, payments, real-time)
|
||||
- Any project where you'd Google "how to build a [X]" before starting
|
||||
|
||||
**Skip research-project for:**
|
||||
- Well-defined specs ("build exactly this API")
|
||||
- Simple tools/utilities with clear scope
|
||||
- Adding features to existing codebases (use research-phase instead)
|
||||
- Domains you've built in many times before
|
||||
</when_to_use>
|
||||
|
||||
<success_criteria>
|
||||
- [ ] PROJECT.md validated
|
||||
- [ ] Domain identified from project description
|
||||
- [ ] Research questions determined and approved
|
||||
- [ ] Parallel research agents spawned
|
||||
- [ ] All research documents created in .planning/research/
|
||||
- [ ] SUMMARY.md includes roadmap implications
|
||||
- [ ] Research committed to git
|
||||
- [ ] User knows next step (create-roadmap)
|
||||
</success_criteria>
|
||||
Reference in New Issue
Block a user