gsd-check-todos
A task manager for listing and selecting pending items from project todo lists.
Install
mkdir -p .claude/skills/gsd-check-todos && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13535" && unzip -o skill.zip -d .claude/skills/gsd-check-todos && rm skill.zipInstalls to .claude/skills/gsd-check-todos
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.
List pending todos and select one to work onKey capabilities
- →List all pending todos
- →Allow interactive selection of a todo
- →Load full context for the selected todo
- →Perform roadmap correlation checking
- →Route to appropriate actions for todos
- →Update `STATE.md` and commit changes
How it works
The skill lists pending todos, allows interactive selection, loads the full context for the chosen todo, performs roadmap correlation, and routes to appropriate actions, updating `STATE.md` and committing changes.
Inputs & outputs
When to use gsd-check-todos
- →Listing pending development tasks
- →Selecting a task to work on
- →Managing project todo backlog
About this skill
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-check-todos. - Treat all user text after
$gsd-check-todosas{{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→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
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_inputis 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: falseby 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>
Routes to the check-todos workflow which handles:
- Todo counting and listing with area filtering
- Interactive selection with full context loading
- Roadmap correlation checking
- Action routing (work now, add to phase, brainstorm, create phase)
- STATE.md updates and git commits </objective>
<execution_context> @D:/code/Project/tablez-demo2-allByAi/.codex/get-shit-done/workflows/check-todos.md </execution_context>
<context> Arguments: {{GSD_ARGS}} (optional area filter)Todo state and roadmap correlation are loaded in-workflow using init todos and targeted reads.
</context>
The workflow handles all logic including:
- Todo existence checking
- Area filtering
- Interactive listing and selection
- Full context loading with file summaries
- Roadmap correlation checking
- Action offering and execution
- STATE.md updates
- Git commits
When not to use it
- →When `request_user_input` is rejected in Execute mode without presenting a plain-text numbered list
- →When proceeding without a user answer unless explicitly allowed by flags or workflow contract
- →When writing workflow artifacts before user answers plain-text questions
Limitations
- →Requires user interaction for selection unless non-interactive flags are set
- →Does not write workflow artifacts until user questions are answered
- →Translates `AskUserQuestion` to `request_user_input` with specific parameter mapping
How it compares
This skill provides an interactive, context-rich workflow for managing and acting on todos, integrating selection, context loading, and action routing, which is more structured than simply listing tasks.
Compared to similar skills
gsd-check-todos side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-check-todos (this skill) | 0 | 4mo | No flags | Beginner |
| linear | 10 | 2mo | No flags | Beginner |
| zapier-workflows | 11 | 8mo | Review | Beginner |
| attio-skill-generator | 7 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by AdityaArote
View all by AdityaArote →You might also like
linear
lobehub
Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
attio-skill-generator
kesslerio
Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.
automation-brainstorm
MacroMan5
Interactive workflow design advisor for Power Automate, n8n, Make, Zapier and other platforms. Guides users through planning automation workflows with smart questions about triggers, actions, data flow, and error handling. Uses research sub-agent to find best practices and generates detailed implementation plan. Triggers when user mentions "create workflow", "build flow", "design automation", "need ideas for", or describes workflow requirements without having a complete design.
daily-briefing
anthropics
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
jira
davila7
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.