gsd-new-project

Automate new project setup by generating planning artifacts and phased roadmaps.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-new-project-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-project
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-new-project
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-new-project-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the friction of starting a new project by guiding you through early decisions and generating a complete planning workspace with research, requirements, and a phased roadmap.

Core Features & Use Cases

  • Guided initialization: Runs a unified flow of questioning to gather deep context before planning.
  • Optional domain research: Creates a research folder when needed to inform requirements and scope.
  • Structured project artifacts: Generates project context, configuration, requirements, roadmap, and a persistent state file to support execution afterward.

Quick Start

Run gsd-new-project with the --auto flag to automatically gather configuration, generate PROJECT.md plus requirements and a roadmap, then proceed by running /gsd-plan-phase 1 for execution.

Frequently Asked Questions about gsd-new-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate project scaffolding with requirements and roadmap planning?

Automated project scaffolding generates structured artifacts like PROJECT.md, REQUIREMENTS.md, and ROADMAP.md through a guided initialization flow. It collects deep context using unified questioning and optional domain research to produce a complete planning workspace for execution.

Can I run project initialization automatically without manual questioning?

Yes, you can run project initialization automatically using the --auto flag. This automatically gathers configuration and generates the project context, requirements, roadmap, and persistent state files without manual questioning.

What files are needed for project state management during workflow automation?

Project state management requires writing .planning/PROJECT.md, .planning/config.json, .planning/REQUIREMENTS.md, .planning/ROADMAP.md, and .planning/STATE.md. These files maintain persistent state and honor workflow gates for validation and commit routing.

Does domain research inform scoped requirements before roadmap planning?

Yes, optional domain research creates a dedicated research folder to inform requirements and scope before generating the roadmap. This ensures the phased roadmapping is based on relevant domain context gathered during the initialization flow.

What is the best way to transition from roadmap planning to execution?

The best way to transition from roadmap planning to execution is to proceed by running the phase execution command after generating the roadmap. Once the planning workspace and persistent state file are created, you execute the first phase of the roadmap.

Are there limitations when using workflow gates for validation and commit routing?

Workflow gates enforce validation and commit routing by requiring the persistent state file to be present and updated. Limitations arise if the planning artifacts are missing or incomplete, which prevents the workflow from proceeding to execution phases.