refactor: remove research-project command

Pre-roadmap research was over-engineered theater:
- 3 parallel subagents producing fragmented output
- Files with unclear consumption points
- Duplicated what research-phase does better (just-in-time)

Deleted:
- commands/gsd/research-project.md
- get-shit-done/workflows/research-project.md
- get-shit-done/templates/project-research.md
- get-shit-done/references/research-subagent-prompts.md

Phase-level research (/gsd:research-phase) remains for niche domains.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Lex Christopherson
2025-12-17 10:01:02 -06:00
parent 65825928cc
commit c2359cdaf3
9 changed files with 9 additions and 1293 deletions

View File

@@ -9,11 +9,9 @@ allowed-tools:
---
<objective>
Create project roadmap, optionally incorporating research findings from /gsd:research-project.
Create project roadmap with phase breakdown.
Roadmaps define the phase breakdown - what work happens in what order. This command can be used:
1. After /gsd:new-project (without research)
2. After /gsd:research-project (with domain research incorporated)
Roadmaps define what work happens in what order. Run after /gsd:new-project.
</objective>
<execution_context>
@@ -57,46 +55,12 @@ If "Cancel": Exit
If "Replace": Continue with workflow
</step>
<step name="check_research">
Check for project research:
```bash
ls .planning/research/*.md 2>/dev/null
```
**If research found:**
Load and summarize each research file:
- ecosystem.md → Key libraries/frameworks recommended
- architecture.md → Architectural patterns to follow
- pitfalls.md → Top 2-3 critical pitfalls to avoid
- standards.md → Standards and conventions to follow
Present summary:
```
Found project research:
Ecosystem: [key libraries/frameworks]
Architecture: [key patterns]
Pitfalls: [top 2-3 to avoid]
Standards: [key conventions]
This will inform phase structure.
```
**If no research found:**
```
No project research found.
Creating roadmap based on PROJECT.md alone.
(Optional: Run /gsd:research-project first for niche/complex domains)
```
</step>
<step name="create_roadmap">
Follow the create-roadmap.md workflow starting from detect_domain step.
The workflow handles:
- Domain expertise detection
- Phase identification (informed by research if present)
- Phase identification
- Research flags for each phase
- Confirmation gates (respecting config mode)
- ROADMAP.md creation
@@ -145,7 +109,6 @@ Roadmap created:
<success_criteria>
- [ ] PROJECT.md validated
- [ ] Research incorporated if present
- [ ] ROADMAP.md created with phases
- [ ] STATE.md initialized
- [ ] Phase directories created