mcpbeat

Gsd New Project

coco-research/gsd-new-project

Initialize a new project with deep context gathering and PROJECT.md

420 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
196
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/coco-research/coco --skill gsd-new-project

The instruction itself

as written by the author

<runtime_note>

Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API.

</runtime_note>

<context>

Flags:

  • --auto — Automatic mode. After config questions, runs research → requirements → roadmap without further interaction. Expects idea document via @ reference.

</context>

<objective>

Initialize a new project through unified flow: questioning → research (optional) → requirements → roadmap.

Creates:

  • .planning/PROJECT.md — project context
  • .planning/config.json — workflow preferences
  • .planning/research/ — domain research (optional)
  • .planning/REQUIREMENTS.md — scoped requirements
  • .planning/ROADMAP.md — phase structure
  • .planning/STATE.md — project memory

After this command: Run /gsd-plan-phase 1 to start execution.

</objective>

<execution_context>

@$HOME/.claude/get-shit-done/workflows/new-project.md

@$HOME/.claude/get-shit-done/references/questioning.md

@$HOME/.claude/get-shit-done/references/ui-brand.md

@$HOME/.claude/get-shit-done/templates/project.md

@$HOME/.claude/get-shit-done/templates/requirements.md

</execution_context>

<process>

Execute the new-project workflow from @$HOME/.claude/get-shit-done/workflows/new-project.md end-to-end.

Preserve all workflow gates (validation, approvals, commits, routing).

</process>

How to use it

Copy the folder

Take coco-research/gsd-new-project from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.