gsd-new-project

Initialize new project workflows and generate planning artifacts.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-new-project-rkz91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-project
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-new-project
Command: npx skills add https://github.com/rkz91/coco --skill gsd-new-project-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize a new project with deep context gathering and a centralized planning structure to accelerate kickoff and maintain project memory across cycles.

Core Features & Use Cases

  • Unified project setup that creates a central planning directory with essential documents (PROJECT.md, ROADMAP.md, REQUIREMENTS.md, STATE.md, and config.json).
  • Context gathering prompts to align stakeholders and capture essential project constraints, goals, and risks.
  • Auto-generated baseline roadmap and memory to support ongoing planning and decision making.

Quick Start

Run the gsd-new-project command to create the .planning structure and baseline documents.

Frequently Asked Questions about gsd-new-project

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

FAQPage Schema
How do I initialize a new project with structured requirements and a roadmap?

To initialize a new project, this workflow gathers deep context and generates baseline planning artifacts, creating a centralized .planning directory with PROJECT.md, ROADMAP.md, REQUIREMENTS.md, STATE.md, and config.json to align stakeholders and capture constraints.

What is the best way to gather context and align stakeholders before starting software development?

Context gathering for software development is handled through structured prompts that capture goals, constraints, and risks, outputting a unified set of planning documents that establish project memory and accelerate kickoff across teams.

Can I use this project setup workflow for both software and product initiatives?

Yes, the project setup workflow applies to both software and product initiatives, generating structured context, requirements, and roadmaps across teams to support ongoing planning and decision making for any structured initiative.

How do I create a centralized planning directory with baseline documents for my team?

Creating a centralized planning directory is done by running the command, which automatically generates baseline documents including PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md along with optional research outputs and memory.

Does this project initialization approach require any external dependencies or components?

No, the project initialization workflow requires no external dependencies or components to set up the planning structure, relying solely on context gathering prompts to generate the required markdown and configuration files.