gsd-add-todo

Capture conversation ideas as structured todos with duplicate detection.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-add-todo-coco-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-todo
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-add-todo
Command: npx skills add https://github.com/coco-research/coco --skill gsd-add-todo-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures ideas, tasks, or issues that emerge during a GSD session and turns them into a structured todo for later follow-up, so nothing important gets lost in conversation.

Core Features & Use Cases

  • Conversation Capture: Converts an optional prompt or live discussion into a concrete todo item.
  • Workflow-Driven Organization: Uses the add-todo workflow to handle directory setup, content extraction, area inference, duplicate detection, and file creation.
  • Project Hygiene: Updates state tracking and supports committing the new todo so the work stays visible and actionable.
  • Use Case: A developer notices a bug, design change, or research follow-up during a chat and wants it recorded in the right area without manual sorting.

Quick Start

Ask the agent to capture the current idea as a todo and route it through the add-todo workflow.

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 conversation context as a trackable todo item?

To capture conversation context as a trackable todo, the Skill extracts ideas, tasks, or issues from your live discussion and translates them into a structured todo file. It uses workflow-driven directory creation and area inference to organize the follow-up work automatically.

How do I avoid duplicate todos when capturing tasks from a project chat?

To avoid duplicate todos when capturing tasks from a project chat, the workflow applies built-in duplicate detection before creating a new file. It checks existing project state and incoming conversation context to ensure only unique, actionable follow-up items are recorded.

Can I automatically commit new todos to my git repository?

Yes, you can commit new todos to your git repository. The workflow handles project hygiene by updating state tracking files and supporting git commits, ensuring the newly captured todo remains visible and actionable in your project history.

What is the best way to turn a bug noticed during a chat into an actionable todo?

The best way to turn a noticed bug into an actionable todo is to route the conversation context through the add-todo workflow. It extracts the issue details, infers the correct project area, creates the file, and updates the project state without manual sorting.

Does this todo capture workflow require manual directory setup?

No, this todo capture workflow does not require manual directory setup. It relies on workflow-driven directory creation to handle file paths and project state automatically, extracting content and organizing the structured todo in the correct area.

Why should I use a structured todo workflow instead of manually noting issues during a session?

You should use a structured todo workflow instead of manual notes to ensure nothing gets lost in conversation. It automatically handles directory setup, duplicate detection, and STATE.md updates, keeping project hygiene intact and follow-up work visible across your git history.