- Removed roadmap_and_state step from new-project command - new-project now offers research-project or create-roadmap as next steps - Updated help.md with new 5-step Quick Start flow - Documented research-project and create-roadmap commands in help 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
3.5 KiB
description, allowed-tools
| description | allowed-tools | ||||
|---|---|---|---|---|---|
| Initialize a new project with deep context gathering and PROJECT.md |
|
This is the most leveraged moment in any project. Deep questioning here means better plans, better execution, better outcomes.
Creates .planning/ with PROJECT.md and config.json.
<execution_context>
@/.claude/get-shit-done/references/principles.md
@/.claude/get-shit-done/references/questioning.md
@/.claude/get-shit-done/templates/project.md
@/.claude/get-shit-done/templates/config.json
</execution_context>
# Abort if project exists
[ -d .planning ] && echo "Project already initialized. Use /gsd:progress" && exit 1
# Initialize git
[ -d .git ] || git init
Then use AskUserQuestion to cover the 9 domains (project type, problem, audience, success, constraints, scope, current state, decisions, open questions).
Skip domains already clear from user input. Probe for specifics on vague answers.
Decision gate (MUST have all 3 options):
Header: "Ready?"
Options:
1. "Create PROJECT.md" - Finalize
2. "Ask more questions" - Dig into uncovered domains
3. "Let me add context" - User shares more
If "Ask more questions" → ask about 2-3 uncovered domains → return to gate. Loop until "Create PROJECT.md" selected.
Synthesize all context into `.planning/PROJECT.md` using the template from `templates/project.md`.Do not compress. Capture everything gathered.
Ask workflow mode preference:Use AskUserQuestion:
- header: "Mode"
- question: "How do you want to work?"
- options:
- "Interactive" - Confirm at each step
- "YOLO" - Auto-approve, just execute
Create .planning/config.json with chosen mode using templates/config.json structure.
[One-liner from PROJECT.md]
Creates PROJECT.md with vision and requirements. EOF )"
</step>
<step name="done">
Project initialized:
- Project: .planning/PROJECT.md
- Config: .planning/config.json (mode: [chosen mode])
What's next?
- Research domain ecosystem (/gsd:research-project) - For niche/complex domains
- Create roadmap (/gsd:create-roadmap) - Skip research, go straight to planning
- Done for now
If user selects "Research domain ecosystem" → invoke `/gsd:research-project`
If user selects "Create roadmap" → invoke `/gsd:create-roadmap`
</step>
</process>
<output>
- `.planning/PROJECT.md`
- `.planning/config.json`
</output>
<success_criteria>
- [ ] Deep questioning completed (not rushed)
- [ ] PROJECT.md captures full context
- [ ] config.json has workflow mode
- [ ] All committed to git
</success_criteria>