gsd-new-project

Automating project initialization involves gathering context to generate structured planning artifacts like PROJECT.md, REQUIREMENTS.md, and ROADMAP.md. This establishes a unified workflow by running a single command to produce all necessary files for a repeatable project setup.

Deep context planning requires generating planning artifacts such as .planning/PROJECT.md, config.json, ROADMAP.md, REQUIREMENTS.md, and STATE.md. These files capture project context, requirements, and roadmap development to establish a unified workflow.

Creating a project roadmap and requirements document from scratch is done by running a project initialization command that coordinates questions, gathers requirements, and automatically outputs .planning/ROADMAP.md and .planning/REQUIREMENTS.md.

Yes, the project initialization workflow supports optional research through a dedicated .planning/research/ directory. This allows you to capture domain research, ideas, and references alongside your core planning artifacts.

The best way to set up a unified workflow for new initiatives is to automate end-to-end project initialization. This gathers context and generates standard planning files, enabling execution with a plan-phase command to start the first planning phase.

Yes, you can start the first planning phase immediately by executing the $gsd-plan-phase 1 command. This enables execution right after the initialization workflow generates your .planning/STATE.md and other project artifacts.