gsdl-create-plan
Generate Task List from PRD
Generates a detailed, step-by-step task list in Markdown format based on an existing Product Requirements Document (PRD). The task list guides a developer through implementation with parent tasks and detailed sub-tasks.
Prerequisites
Before generating a task list:
- Project exists: The project should have its own folder at
.planning/[project-name]/ - PRD exists: Ensure the PRD file exists at
.planning/[project-name]/prd-[feature-name].md
Output
The task list will be saved as:
- Format: Markdown (
.md) - Location:
.planning/[project-name]/ - Filename:
tasks-[prd-file-name].md(e.g.,tasks-prd-user-profile-editing.md) - Full Path Example:
.planning/my-cool-project/tasks-prd-user-authentication.md
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-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