agentleFS
adrianoanthonymma16-boopadrianoanthonymma16-boop/opencode-agents/skills/gsd-new-project/SKILL.md

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

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
  1. Very specific:

    Copilot (VS Code): Use vscode_askquestions wherever this workflow calls question.

    line 7
  2. Very specific:

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

    line 26

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

<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>

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.