| name | gsd-new-project |
| description | Initialize a new project with deep context gathering and PROJECT.md |
<augment_skill_adapter>
A. Skill Invocation
- This skill is invoked when the user mentions
gsd-new-project or describes a task matching this skill.
- Treat all user text after the skill mention as
{{GSD_ARGS}}.
- If no arguments are present, treat
{{GSD_ARGS}} as empty.
B. User Prompting
When the workflow needs user input, prompt the user conversationally:
- Present options as a numbered list in your response text
- Ask the user to reply with their choice
- For multi-select, ask for comma-separated numbers
C. Tool Usage
Use these Augment tools when executing GSD workflows:
launch-process for running commands (terminal operations)
str-replace-editor for editing existing files
view for reading files and listing directories
save-file for creating new files
grep for searching code (or use MCP servers for advanced search)
web-search, web-fetch for web queries
add_tasks, view_tasklist, update_tasks for task management
D. Subagent Spawning
When the workflow needs to spawn a subagent:
- Use the built-in subagent spawning capability
- Define agent prompts in
.augment/agents/ directory
</augment_skill_adapter>
<runtime_note>
Copilot (VS Code): Use vscode_askquestions wherever this workflow calls conversational prompting. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API.
</runtime_note>
**Flags:**
- `--auto` — Automatic mode. After config questions, runs research → requirements → roadmap without further interaction. Expects idea document via @ reference.
Initialize a new project through unified flow: questioning → research (optional) → requirements → roadmap.
Creates:
.planning/PROJECT.md — project context
.planning/config.json — workflow preferences
.planning/research/ — domain research (optional)
.planning/REQUIREMENTS.md — scoped requirements
.planning/ROADMAP.md — phase structure
.planning/STATE.md — project memory
After this command: Run /gsd-plan-phase 1 to start execution.
<execution_context>
@/home/delorenj/code/bhappy/.augment/get-shit-done/workflows/new-project.md
@/home/delorenj/code/bhappy/.augment/get-shit-done/references/questioning.md
@/home/delorenj/code/bhappy/.augment/get-shit-done/references/ui-brand.md
@/home/delorenj/code/bhappy/.augment/get-shit-done/templates/project.md
@/home/delorenj/code/bhappy/.augment/get-shit-done/templates/requirements.md
</execution_context>
Execute the new-project workflow from @/home/delorenj/code/bhappy/.augment/get-shit-done/workflows/new-project.md end-to-end.
Preserve all workflow gates (validation, approvals, commits, routing).