gsd-new-project

Initialize a new project by generating a planning scaffold with PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/giovannimnz/gsd-caveman-hermes --skill gsd-new-project-giovannimnz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-project
Source: https://github.com/giovannimnz/gsd-caveman-hermes/tree/main/skills/gsd-new-project
Command: npx skills add https://github.com/giovannimnz/gsd-caveman-hermes --skill gsd-new-project-giovannimnz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the initial project setup by gathering context and producing a ready-to-use planning scaffold, saving time and reducing misalignment at kickoff.

Core Features & Use Cases

  • Auto-create a planning scaffold including PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md.
  • Integrate questioning, research, and requirements generation into a unified initial-flow.
  • Provide a ready starting point for team alignment, scope definition, and roadmap planning.

Quick Start

Run the command to initialize a new project and generate the planning directory structure.

Frequently Asked Questions about gsd-new-project

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

FAQPage Schema
How do I create a project planning scaffold with roadmap and requirements files?

To create a project planning scaffold, this Skill initializes a new project by gathering context and automatically generating PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md files within a .planning directory to structure your kickoff.

What do I need to set up before initializing project planning files?

Before initializing project planning files, you need an existing git repository setup and a designated .planning directory to hold the generated PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md outputs.

How does automated project initialization handle scope definition and team alignment?

Automated project initialization handles scope definition and team alignment by integrating questioning, research, and requirements generation into a unified initial-flow, producing a ready starting point for roadmap planning.

Can I use this project initialization flow for an existing codebase?

This project initialization flow is designed to be applied at project kickoff to auto-create a planning scaffold for new initiatives, rather than retroactively fitting an existing codebase with planning documents.

What is the best way to bootstrap a new project context and planning flow?

The best way to bootstrap a new project context and planning flow is to run the initialization command, which gathers context and produces a ready-to-use planning scaffold to reduce misalignment at kickoff.

Why does project initialization require a git repository and .planning directory?

Project initialization requires a git repository and .planning directory to establish version control and a dedicated structural location for the generated PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md files.