gsdl-create-prd
Create PRD
Generates a detailed Product Requirements Document (PRD) in Markdown format, based on a project's seed file and user input. The PRD is designed to be clear, actionable, and suitable for a junior developer to understand and implement.
Prerequisites
Before creating a PRD, verify:
- Project exists: The project should have its own folder at
.planning/[project-name]/ - Seed file exists: Check for
.planning/[project-name]/seed.mdcontaining the initial idea or concept
If the project structure doesn't exist, create it first following the project-setup conventions.
Process
Step 1: Read the Seed File from Disk
Read .planning/[project-name]/seed.md directly from disk — do not rely on any in-context version. The user may have edited the file after the project setup phase. Always use the on-disk content as the source of truth.
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-setup-project
Set up new project structure with seed file for research workspace. Use when the user wants to start a new project, create a project structure, initialize a new idea, or mentions starting something new.
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-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