gsdl-setup-project
Setup Project
Creates a standardized project structure for new ideas, prototypes, or tools in the research workspace. Each project gets its own isolated folder with task tracking and documentation structure.
Goal
Ensure every new idea, prototype, or tool is organized into its own dedicated folder structure. This keeps the workspace clean and ensures each project has proper context, requirements, and task tracking from the start.
Project Structure Requirements
Every new project must include:
- Isolated Project Folder: Dedicated directory under
.planning/(e.g.,.planning/project-name/) - Seed File: Initial idea capture at
.planning/project-name/seed.md - Containment: All planning files (seed, PRDs, task lists, decisions) stay within
.planning/[project-name]/
Setup Workflow
Step 1: Identify Project Name
More from nsantini/gsdl
gsdl
Get Shit Done (GSD) orchestrator. Runs the full project pipeline from idea to implementation to documentation: setup → PRD → task list → implementation → decisions doc. Use when the user wants to build something end-to-end, says \"let's GSD\", \"build this from scratch\", \"get shit done\", or wants to run the full development workflow. Coordinates gsdl-setup-project, gsdl-create-prd, gsdl-create-plan, gsdl-execute-plan, and gsdl-document-decisions skills. Spawns subagents per parent task during implementation to preserve context. Accepts an optional project name or source URL: /gsdl [project-name] OR /gsdl [linear|notion|slite] [url] OR /gsdl [url].
35gsdl-execute-plan
Execute an implementation plan step-by-step with completion tracking. Use when the user wants to work through a plan, implement tasks sequentially, track progress on a task list, or asks to "execute the plan" or "start implementing".
34gsdl-create-plan
Generate a detailed implementation plan (task list) from a Product Requirements Document (PRD). Use when the user wants to break down a PRD into implementation tasks, create a plan from requirements, generate tasks from a PRD, or asks to "create a plan".
33gsdl-create-prd
Generate a Product Requirements Document (PRD) from a seed file or user input. Use when the user wants to create a PRD, document requirements, formalize a feature spec, or turn an idea into a structured requirements document.
33gsdl-fetch-source
Fetch project context from a Linear ticket, Notion doc, or Slite doc URL. Use when the user provides a Linear, Notion, or Slite URL as the starting point for a GSDL project. Extracts title, description, and structured content from the remote source to pre-populate the seed.md file.
26gsdl-document-decisions
Capture architectural decisions and changes made during a GSDL project into a structured markdown document. Analyzes git history and diffs, extracts key decisions, and optionally pushes the doc to Slite or Notion as a child page. Called by the gsdl orchestrator after all implementation tasks are complete.
19