gsd-add-todo

Capture conversation tasks into markdown todo files with YAML frontmatter.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-add-todo-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-todo
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-add-todo
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-add-todo-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Meetings and conversations often surface action items and ideas that are forgotten or scattered across chat threads; this Skill captures those moments as structured todo files so nothing slips through the cracks.

Core Features & Use Cases

  • Contextual Capture: Extracts task details from the current conversation or an optional description argument and formats them as markdown todos with YAML frontmatter.
  • Repository Integration: Infers area from file paths, ensures directory structure, updates STATE.md, generates slugs, checks for duplicates, and commits changes to git.
  • Use Case: During a GSD session, convert an identified action item into a tracked todo file tied to the appropriate project area for later work.

Quick Start

Create a todo capturing the key task from this conversation, optionally supplying a brief description.

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 action items from a conversation into structured todo files?

Capturing conversation action items into structured todos involves extracting task details and formatting them as markdown files with YAML frontmatter. This Skill generates unique slugs, infers project areas from file paths, detects duplicates, and commits the todo files to git.

What is the best way to track meeting tasks in a git repository without losing context?

The best way to track meeting tasks in a git repository is by creating repository-native todo files that update STATE.md for tracking. This ensures conversation ideas are captured as structured markdown todos tied to the appropriate project area without slipping through the cracks.

How does duplicate detection work when adding new todo items?

Duplicate detection for todo items works by checking newly captured conversation tasks against existing repository files. This prevents action items from being recorded twice, ensuring your task capture workflow maintains a clean and tracked project state.

Do I need a specific workflow directory to use the add-todo task capture feature?

You need the workflow referenced at ~/.claude/get-shit-done/workflows/add-todo.md to use the add-todo task capture feature. This GSD workflow integration ensures directory structure is maintained and STATE.md is updated during the git commit process.

Can I infer project areas from file paths when creating markdown todos?

You can infer project areas from file paths when creating markdown todos. This task capture feature automatically determines the appropriate project area directory, ensuring structured todo items are organized correctly within your git repository.

What are the limitations of using chat-based workflows for task capture?

Using chat-based workflows for task capture requires a git repository environment to commit markdown todo files and update STATE.md. Without the referenced GSD workflow directory structure, the area inference and duplicate detection features cannot operate.