gsdl-execute-plan
Manage Task List
Guides implementation of task lists with structured completion tracking. This skill enforces a disciplined, step-by-step approach to working through tasks generated from PRDs.
Project Context
Task lists are located at .planning/[project-name]/tasks-[prd-name].md. Implementation code lives at the workspace root (not inside .planning/).
Operating Modes
Standard Mode (default)
Work on ONE sub-task at a time. Do NOT start the next sub-task until the user explicitly approves. Stop after each sub-task and wait for "yes", "go", "next", etc.
Batch Mode (GSD orchestrator only)
If your instructions say "BATCH MODE", complete all sub-tasks under your assigned parent task without pausing for approval between sub-tasks. Apply the full completion protocol (mark [x], update task file) after each sub-task, then immediately continue to the next. When the entire parent task is [x], follow the Parent Task Completion protocol (including the git commit), then stop and return a summary — do not start any other parent task.
Completion Protocol
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-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