gsd-add-todo

name	gsd-add-todo
description	Capture idea or task as todo from current conversation context
metadata	{"short-description":"Capture idea or task as todo from current conversation context"}

<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:

• header → header
• question → question
• 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>

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

<execution_context> @/Users/teo/src/tempo/.codex/get-shit-done/workflows/add-todo.md </execution_context>

Arguments: {{GSD_ARGS}} (optional todo description)

State is resolved in-workflow via init todos and targeted reads.

**Follow the add-todo workflow** from `@/Users/teo/src/tempo/.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