Turn conversation insights into actionable todos.

Install

mkdir -p .claude/skills/gsd-add-todo && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12544" && unzip -o skill.zip -d .claude/skills/gsd-add-todo && rm skill.zip

Installs to .claude/skills/gsd-add-todo

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Capture idea or task as todo from current conversation context
62 charsno explicit “when” trigger
Beginner

Key capabilities

  • Capture idea or task as todo
  • Create directory structure for todos
  • Extract content from arguments or conversation
  • Infer area from file paths
  • Detect and resolve duplicate todos
  • Create todo file with frontmatter

How it works

The skill invokes the add-todo workflow, which handles directory creation, content extraction, area inference, duplicate detection, and todo file creation. It also updates `STATE.md` and performs Git commits.

Inputs & outputs

You give it
user text after `$gsd-add-todo` or current conversation context
You get back
a structured todo file with frontmatter, updated `STATE.md`, and Git commits

When to use gsd-add-todo

  • Saving ideas as todos
  • Creating tasks during brainstorming
  • Capturing action items from meetings

About this skill

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-add-todo.
  • Treat all user text after $gsd-add-todo as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • headerheader
  • questionquestion
  • Options formatted as "Label" — description{label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y")spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit (Codex uses per-role config, not inline model selection)
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>
<objective> Capture an idea, task, or issue that surfaces during a GSD session as a structured todo for later work.

Routes to the add-todo workflow which handles:

  • Directory structure creation
  • Content extraction from arguments or conversation
  • Area inference from file paths
  • Duplicate detection and resolution
  • Todo file creation with frontmatter
  • STATE.md updates
  • Git commits </objective>

<execution_context> @/Users/gabrielwillen/VSCode/stateforward/emel/emel.cpp/.codex/get-shit-done/workflows/add-todo.md </execution_context>

<context> Arguments: {{GSD_ARGS}} (optional todo description)

State is resolved in-workflow via init todos and targeted reads. </context>

<process> **Follow the add-todo workflow** from `@/Users/gabrielwillen/VSCode/stateforward/emel/emel.cpp/.codex/get-shit-done/workflows/add-todo.md`.

The workflow handles all logic including:

  1. Directory ensuring
  2. Existing area checking
  3. Content extraction (arguments or conversation)
  4. Area inference
  5. Duplicate checking
  6. File creation with slug generation
  7. STATE.md updates
  8. Git commits
</process>

When not to use it

  • When not capturing an idea, task, or issue during a GSD session
  • When not creating a structured todo
  • When not using the add-todo workflow

Limitations

  • Requires the add-todo workflow to be followed
  • Relies on `AskUserQuestion` and `Task()` for interaction and agent spawning
  • Assumes `STATE.md` updates and Git commits are part of the workflow

How it compares

This workflow provides a structured and automated way to capture ideas as todos, including duplicate detection and Git integration, which is more reliable than simply jotting down notes.

Compared to similar skills

gsd-add-todo side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gsd-add-todo (this skill)03moNo flagsBeginner
notion-meeting-intelligence66moNo flagsIntermediate
resume-handoff36moNo flagsIntermediate
meeting-briefing26moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

notion-meeting-intelligence

openai

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

656

resume-handoff

parcadei

Resume work from handoff document with context analysis and validation

333

meeting-briefing

anthropics

Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.

213

personal-assistant

ailabs-393

This skill should be used whenever users request personal assistance tasks such as schedule management, task tracking, reminder setting, habit monitoring, productivity advice, time management, or any query requiring personalized responses based on user preferences and context. On first use, collects comprehensive user information including schedule, working habits, preferences, goals, and routines. Maintains an intelligent database that automatically organizes and prioritizes information, keeping relevant data and discarding outdated context.

36

digital-brain

muratcankoylan

This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.

15

meeting-sync

amanaiproduct

Sync new Granola meetings to local Knowledge folder. Use during morning planning, when user asks "what should I do today", or asks to review/sync meetings.

13

Search skills

Search the agent skills registry