gsd-add-todo

Capture GSD session ideas as structured todos with area inference and deduplication.

Updated Jan 28, 2025
One-click install
npx skills add https://github.com/aslaii/dotfiles --skill gsd-add-todo-aslaii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-todo
Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-add-todo
Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-add-todo-aslaii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture ideas or tasks surfaced during GSD sessions as structured todos for later work.

Core Features & Use Cases

  • Routes ideas or tasks from conversations into organized todo items.
  • Infers the relevant area and performs duplicate checks to keep todos actionable.
  • Updates state and maintains a changelog via STATE.md and Git commits.

Quick Start

Provide the idea or task from the chat and let the workflow create a structured 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 capture ideas from chat conversations as structured todos?

Capturing ideas from chat as structured todos involves routing conversational text into organized todo items with context and area inference. The workflow extracts content, assigns areas, and performs deduplication to maintain actionable task lists.

How does todo deduplication work when extracting tasks from conversations?

Todo deduplication works by checking newly extracted tasks against existing items before file creation. This process uses slug-based identification and area inference to prevent duplicate todo entries from being committed to your state management workflow.

Can I use state management to track todos directly from real-time GSD sessions?

Yes, state management tracks todos from GSD sessions by updating a STATE.md file and creating Git commits. This ensures conversational ideas are persistently logged as structured, actionable items with inferred areas and context.

What is the best way to organize tasks inferred from project conversations?

Organizing inferred tasks requires directory management and slug-based file creation. By automatically extracting content and assigning areas during conversations, the system routes ideas into structured files and updates the state changelog.

Does extracting todos from chat require manual Git commits and directory setup?

No, extracting todos does not require manual Git commits or directory setup. The workflow automatically handles directory management, slug-based file creation, STATE.md updates, and Git commits after inferring areas and checking for duplicates.

Why are my inferred todo items creating duplicate files in the directory?

Duplicate todo files occur when the deduplication check fails to match new conversational ideas against existing slugs. Proper area inference and consistent slug-based file creation are required to prevent duplicate todo entries during state management updates.