agentleFS
ChianWChianW/C31/skills/utils/gsd-new-project/SKILL.md

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

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

    gsd-next

    Smart entry — detect project state and route to the right next GSD action.

    Also in 3 projects that use this

  • open-gsdSkill

    gsd-onboard

    Guide existing codebase onboarding through mapping, doc ingest, and planning setup

    Also in 3 projects that use this

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
  1. Distinctive:

    Ask the user: "What is your project idea?" (or accept from command arguments).

    line 31
  2. Very specific:

    Use exec to check if memory/.planning/ already exists.

    line 35
  3. Very specific:

    If it exists, warn the user: "memory/.planning/ already exists.

    line 41
  4. Distinctive:

    If the user declines, stop here.

    line 43
  5. Very specific:

    Use the write tool to create each file.

    line 47
  6. Very specific:

    Always ask for confirmation before overwriting memory/.planning/.

    line 169
  7. Very specific:

    Use the write tool to create files (do not use exec for file creation).

    line 170
  8. Distinctive:

    Keep the initial artifacts lightweight.

    line 171
  9. Distinctive:

    If no project name is provided, use a sanitized slug from the project idea or default to "untitled-project".

    line 172

“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

Multilingual Triggers

LanguageTrigger phrases
ENnew 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/null

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.

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 iterate

STATE.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 deferred

config.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 write tool to create files (do not use exec for 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".

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.