gsd-new-project

Initialize new projects by gathering context, defining requirements, and creating planning documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the initialization of new projects by gathering deep context and creating essential planning documents.

Core Features & Use Cases

  • Unified Project Initialization: Guides users through a comprehensive flow from initial questioning to research, requirements, and roadmap creation.
  • Automated Document Generation: Creates .planning/PROJECT.md, .planning/config.json, .planning/REQUIREMENTS.md, .planning/ROADMAP.md, and .planning/STATE.md.
  • Use Case: Kickstart a new software development project by defining its scope, requirements, and initial phases.

Quick Start

Run the gsd-new-project skill to initialize a new project.

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 requirements gathering and roadmap creation?

To initialize a new project, this Skill gathers deep context, conducts research, defines requirements, and creates a structured roadmap. It generates essential planning documents like PROJECT.md, REQUIREMENTS.md, and ROADMAP.md to define the project scope.

What is the best way to automate project initialization and generate planning documents?

Automating project initialization is best handled through automated and interactive modes that process structured input for idea generation. This workflow generates a suite of planning files, including config.json and STATE.md, to establish the foundational project context.

Can I use this project initialization workflow for software development scope definition?

Yes, you can use this workflow to kickstart a new software development project. It guides you through comprehensive context gathering to define the project scope, establish requirements, and outline initial development phases.

Does project initialization require structured input for workflow preferences?

Yes, project initialization requires structured input for idea generation and workflow preferences. Providing this structured context is necessary to accurately generate the planning documents and define the project roadmap.

What planning documents are generated during project setup?

During project setup, the workflow generates five core planning documents: PROJECT.md, config.json, REQUIREMENTS.md, ROADMAP.md, and STATE.md. These files are stored within a dedicated .planning directory structure.

How does context gathering work for new project initialization?

Context gathering for new project initialization works by guiding users through an initial questioning flow and conducting research. This unified process captures the necessary project details to define requirements and create a comprehensive roadmap.