gsd-new-project
Skill1 starsChanged 58 days agoMITView on GitHub
Initialize a new project with deep context gathering and PROJECT.md
5 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- sp1e/claude-skillsedited, first seen Oct 12, 2026
- ChianW/C31their own version, first seen Oct 11, 2026
- open-gsd/get-shit-done-reduxedited, first seen Oct 8, 2026
- open-gsd/gsd-coreedited, first seen Sep 2, 2026
- ZaneL1u/cloud-cli-proxyedited, first seen May 9, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- open-gsd/get-shit-done-redux★ 11k58% same
- open-gsd/gsd-core★ 11k58% same
- ZaneL1u/cloud-cli-proxy★ 5740% same
- sp1e/claude-skills★ 169% same
Wrote their own version · 1
- ChianW/C31★ 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 repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ask-mattSkill
- banner-designSkill
- brandSkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- designSkill
- design-systemSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- git-guardrails-claude-codeSkill
- graphifySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- gsd-add-testsSkill
- gsd-ai-integration-phaseSkill
- gsd-audit-fixSkill
- gsd-audit-milestoneSkill
- gsd-audit-uatSkill
- gsd-autonomousSkill
- gsd-captureSkill
- gsd-cleanupSkill
- gsd-code-reviewSkill
- gsd-complete-milestoneSkill
- gsd-configSkill
- gsd-debugSkill
- gsd-discuss-phaseSkill
- gsd-docs-updateSkill
- gsd-eval-reviewSkill
- gsd-execute-phaseSkill
- gsd-exploreSkill
- gsd-extract-learningsSkill
- gsd-fastSkill
- gsd-forensicsSkill
- gsd-graphifySkill
- gsd-healthSkill
- gsd-helpSkill
- gsd-importSkill
- gsd-inboxSkill
- gsd-ingest-docsSkill
- gsd-managerSkill
- gsd-map-codebaseSkill
- gsd-mempalace-captureSkill
- gsd-mempalace-recallSkill
- gsd-milestone-summarySkill
- gsd-mvp-phaseSkill
- gsd-new-milestoneSkill
- gsd-nextSkill
- gsd-ns-contextSkill
- gsd-ns-ideateSkill
- gsd-ns-manageSkill
- gsd-ns-projectSkill
- gsd-ns-reviewSkill
- gsd-ns-workflowSkill
- gsd-onboardSkill
- gsd-pause-workSkill
- gsd-phaseSkill
- gsd-plan-phaseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Copilot (VS Code): Use vscode_askquestions wherever this workflow calls question.
- Very specific: line 26
After this command: Run /gsd-plan-phase 1 to start execution.
“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
<runtime_note>
Copilot (VS Code): Use vscode_askquestions wherever this workflow calls question. 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/tony/.config/opencode/gsd-core/workflows/new-project.md @/home/tony/.config/opencode/gsd-core/references/questioning.md @/home/tony/.config/opencode/gsd-core/references/ui-brand.md @/home/tony/.config/opencode/gsd-core/templates/project.md @/home/tony/.config/opencode/gsd-core/templates/requirements.md </execution_context>
<process>
Execute end-to-end.
Preserve all workflow gates (validation, approvals, commits, routing).
</process>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.

