gsd-new-project

To create structured project planning artifacts before development, you can use guided initialization to interactively capture context and automatically generate a PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md. This ensures a consistent project baseline for execution.

The best way to initialize a new project with a roadmap is to run an automated project setup that gathers context and generates a standardized .planning directory. This produces consistent requirements and roadmap files while preserving validation and approval gates.

Yes, you can automatically generate a project state file and config by running project initialization with an idea reference or an auto flag. This creates .planning/config.json and .planning/STATE.md alongside your requirements and roadmap documentation.

Guided project initialization does preserve workflow validation, approval, commit, and routing gates. This ensures that team handoffs and verification processes remain intact within the generated project baseline and state tracking files.

To kickstart a project with structured planning, you need files including .planning/PROJECT.md, config.json, REQUIREMENTS.md, ROADMAP.md, and STATE.md. Optional research folders can also be generated to capture domain context during initialization.

Product managers should use automated documentation for project setup to eliminate friction and convert ideas into documented plans. It produces standardized planning artifacts, allowing teams to move straight into execution with a consistent roadmap and requirements baseline.