gsd-new-project

Initialize a project planning workspace with guided discovery and structured markdown deliverables.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of starting a new project by guiding you through structured discovery, so you can turn an idea into a clear plan without missing important context.

Core Features & Use Cases

  • Guided Project Intake: Collects the key background, goals, and constraints needed to define a new initiative.
  • Optional Research Flow: Supports deeper domain research when the project needs more context before planning.
  • Planning Outputs: Produces project context, requirements, roadmap, and project memory files for execution readiness.
  • Use Case: A team lead can use this Skill to turn a rough product idea into a documented project plan that is ready for phased implementation.

Quick Start

Use the gsd-new-project skill to help me initialize a new project and create the planning documents from my idea.

Frequently Asked Questions about gsd-new-project

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

FAQPage Schema
How do I turn a rough software project idea into a structured roadmap?

To turn a rough software project idea into a structured roadmap, you need guided project intake that captures background, goals, and constraints to produce phased planning documents. This skill facilitates that discovery process to ensure execution readiness without missing context.

What is guided project intake for greenfield software engineering?

Guided project intake for greenfield software engineering is a structured discovery process that collects core context, defines initiative scope, and applies workflow gates. It ensures all key background and constraints are documented before execution begins.

How do I gather requirements and create planning deliverables for a new project?

You gather requirements and create planning deliverables by applying guided questioning and optional research flows. This generates structured markdown files for project context, requirements, and roadmaps to support seamless handoff and configuration persistence.

Can I use this guided planning workflow for greenfield projects only?

Yes, this guided planning workflow applies specifically to greenfield software projects that need scoped requirements and phased roadmap creation. It initializes a new project planning workspace to capture the core context needed to start execution.

What's the best way to document project context and memory for development handoff?

The best way to document project context and memory for development handoff is to use a structured intake process that generates persistent configuration and markdown deliverables. This captures goals and constraints for continuous execution readiness.

Do I need to conduct domain research before creating a software project roadmap?

You do not always need to conduct domain research before creating a software project roadmap, but an optional research flow supports deeper context gathering when required. This ensures scoped requirements are fully defined before phased implementation begins.