gsd-new-project
Skill1 starsChanged 3 months agoMITView on GitHub
Output language: Respond automatically in the user's conversation language. Initialize a new project with GSD (Get Stuff Done) planning artifacts. Ask the user: "What is your project idea?" (or accept from command arguments). Use exec to check if memory/.planning/ already exists. If it exists, warn the user: "memory/.planning/ already exists. Continuing will overwrite existing planning files. Proceed? (yes/no)" If the user declines, stop here. Use the write tool to create each file. Replace {{project_name}}, {{project_idea}}, {{user}}, and {{date}} with actual…
5 other projects use a version of this.
Adopted by
Most recently taken up by
- sp1e/claude-skillstheir own version, first seen Oct 12, 2026
- open-gsd/get-shit-done-reduxtheir own version, first seen Oct 8, 2026
- adrianoanthonymma16-boop/opencode-agentstheir own version, first seen Sep 16, 2026
- open-gsd/gsd-coretheir own version, first seen Sep 2, 2026
- ZaneL1u/cloud-cli-proxytheir own version, first seen May 9, 2026
Used with
Projects with it also use gsd-next and gsd-onboard.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
open-gsdSkillgsd-next
Smart entry — detect project state and route to the right next GSD action.
Also in 3 projects that use this
open-gsdSkillgsd-onboard
Guide existing codebase onboarding through mapping, doc ingest, and planning setup
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- open-gsd/get-shit-done-redux★ 11ksame name
- open-gsd/gsd-core★ 11ksame name
- ZaneL1u/cloud-cli-proxy★ 57same name
- adrianoanthonymma16-boop/opencode-agents★ 1same name
- sp1e/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- C31-1stSkill
- C31-adopt-projectSkill
- C31-brainstormSkill
- C31-coding-disciplineSkill
- C31-compound-refreshSkill
- C31-compoundSkill
- C31-context-engineeringSkill
- C31-curatorSkill
- c31-daily-intelSkill
- C31-debugSkill
- c31-devSkill
- C31-grillSkill
- C31-lfgSkill
- C31-planSkill
- C31-researchSkill
- C31-specSkill
- C31-stormSkill
- C31-strategySkill
- C31-workflow-bug-reproductionSkill
- C31-workSkill
- rl-workflowSkill
- C31-cvideoSkill
- c31-loopSkill
- c31-sxsSkill
- teachSkill
- video-content-analysisSkill
- agent-reachSkill
- kimiimSkill
- skillhub-preferenceSkill
- c31-communitySkill
- c31-growSkill
- c31-gutcheckSkill
- c31-marketSkill
- c31-mvpSkill
- c31-priceSkill
- c31-processSkill
- c31-sellSkill
- c31-validateSkill
- c31-valuesSkill
- growth-hackerSkill
- c31-improve-codebase-architectureSkill
- C31-multi-reviewSkill
- C31-review-adversarialSkill
- C31-review-architectureSkill
- C31-review-securitySkill
- C31-reviewSkill
- c31-wizardSkill
- external-privacy-guardSkill
- find-skillsSkill
- gsd-map-codebaseSkill
- gsd-progressSkill
- gsd-quickSkill
- gsd-shipSkill
- humanize-aiSkill
- time-awarenessSkill
- worker-safetySkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Ask the user: "What is your project idea?" (or accept from command arguments).
- Very specific: line 35
Use exec to check if memory/.planning/ already exists.
- Very specific: line 41
If it exists, warn the user: "memory/.planning/ already exists.
- Distinctive: line 43
If the user declines, stop here.
- Very specific: line 47
Use the write tool to create each file.
- Very specific: line 169
Always ask for confirmation before overwriting memory/.planning/.
- Very specific: line 170
Use the write tool to create files (do not use exec for file creation).
- Distinctive: line 171
Keep the initial artifacts lightweight.
- Distinctive: line 172
If no project name is provided, use a sanitized slug from the project idea or default to "untitled-project".
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Multilingual Triggers
| Language | Trigger phrases |
| EN | new project, 新项目, init project, start project, bootstrap project |
| ZH | 新项目, 初始化项目 |
| JA | 新規プロジェクト, プロジェクト開始 |
Output language: Respond automatically in the user's conversation language.
gsd-new-project
Initialize a new project with GSD (Get Stuff Done) planning artifacts.
When to Use
- User says "new project", "新项目", "init project", "start project"
- User wants to bootstrap a structured project workspace
Workflow
Step 1: Gather Project Idea
Ask the user: "What is your project idea?" (or accept from command arguments).
Step 2: Check for Existing Planning Directory
Use exec to check if memory/.planning/ already exists.
ls -la memory/.planning/ 2>/dev/nullIf it exists, warn the user: "memory/.planning/ already exists. Continuing will overwrite existing planning files. Proceed? (yes/no)"
If the user declines, stop here.
Step 3: Create Planning Artifacts
Use the write tool to create each file.
PROJECT.md
---
created: {{date}}
status: active
---
# {{project_name}}
## Vision
{{project_idea}}
## Goals
- [ ] Primary goal to be defined
## Context
- **Owner**: {{user}}
- **Started**: {{date}}
## Notes
_Add project notes here._ROADMAP.md
# Roadmap
## Phase 0: Foundation
- Project setup and planning
## Phase 1: Exploration
- Research and prototyping
## Phase 2: Build
- Core implementation
## Phase 3: Polish
- Testing and refinement
## Phase 4: Ship
- Launch and iterateSTATE.md
# Current State
**Phase**: 0
## Active Tasks
_None yet._
## Blockers
_None._
## Last Updated
{{date}}REQUIREMENTS.md
# Requirements
## v1 (MVP)
- Core functionality to deliver initial value
## v2 (Next)
- Enhancements after initial feedback
## Out of Scope
- Features explicitly deferredconfig.json
{
"project_name": "{{project_name}}",
"created": "{{date}}",
"default_model": "kimi/k2p6",
"planning_dir": "memory/.planning",
"auto_checkpoint": true
}Replace {{project_name}}, {{project_idea}}, {{user}}, and {{date}} with actual values.
Step 4: Confirm Output
Report back to the user:
✅ Project initialized: {{project_name}}
Created files:
- memory/.planning/PROJECT.md
- memory/.planning/ROADMAP.md
- memory/.planning/STATE.md
- memory/.planning/REQUIREMENTS.md
- memory/.planning/config.json
Next: Fill in PROJECT.md with details, then run `gsd-plan` to build a task plan.Rules
- Always ask for confirmation before overwriting
memory/.planning/. - Use the
writetool to create files (do not useexecfor file creation). - Keep the initial artifacts lightweight; they are templates to be filled in.
- If no project name is provided, use a sanitized slug from the project idea or default to "untitled-project".
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

