gsd-add-todo

Capture ideas as structured todos with frontmatter and commit changes.

8|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-add-todo-d0nmega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-todo
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-add-todo
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-add-todo-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture ideas, tasks, or issues from a GSD session and convert them into structured todos for later work.

Core Features & Use Cases

  • Directory structure creation and lifecycle management for todos
  • Content extraction from arguments or conversation context to populate todo metadata
  • Area inference from file paths and duplicate detection to avoid churn
  • Todo file creation with frontmatter, STATE.md updates, and Git commits
  • Deterministic workflow routing through the add-todo process

Quick Start

Provide an idea or task description as an argument to the add-todo workflow to create a new todo.

Frequently Asked Questions about gsd-add-todo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn ideas from a conversation into trackable todos?

To turn ideas into trackable todos, you provide a task description as an argument to the workflow. It extracts content from conversation context and creates structured todo files for later work.

What is the best way to capture tasks during a chat session without losing context?

Capturing tasks during a chat session involves extracting content from conversation context and converting it into structured todos. This workflow ensures deterministic execution and saves traceable history via Git commits.

How does task management automation infer areas and avoid duplicate todos?

Task management automation infers areas from file paths and performs duplicate detection to avoid churn. It ensures new todos are slugged correctly and organized within the correct directories.

Do I need Git to manage todo lifecycle and state updates?

Yes, Git is required to manage todo lifecycle and state updates. The workflow commits changes automatically after updating STATE.md to maintain a traceable history of todos.

What limitations exist when creating structured todos from chat arguments?

A limitation when creating structured todos is that content extraction relies on arguments or conversation context. If context is ambiguous, the inferred area or slugged todo might not match expectations.