create-task-list.template

Codex Runtime Compatibility

This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:

• AskUserQuestion => ask the user directly in chat.
• WebSearch/WebFetch => use available web tools (search_query, open, find) and cite links.
• Read/Write => use shell/filesystem tools in this workspace.
• Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
• Keep intent and output format identical; only adapt execution mechanics.

---

description: Create intelligent task list with codebase exploration and clarifying questions type: project complexity: medium model: opus argument-hint: [task or feature description] allowed-tools:

• Read
• Grep
• Glob
• Task
• TaskCreate
• TaskUpdate
• TaskList
• AskUserQuestion
• Write

---

/create-task-list - Intelligent Task List Generator

Create a comprehensive task list with codebase exploration, clarifying questions, and persistent testing instructions.

---

QUICK START

/create-task-list fix the login page redirect bug
/create-task-list add dark mode to the settings panel
/create-task-list for issue #123                      # Analyze issue, generate tasks
/create-task-list for issue #123 --use-existing-tasks # Use issue's task checklist
/create-task-list

---

FLAGS & ARGUMENTS

Argument	Description
for issue #[N]	Pull context from GitHub issue #N
--use-existing-tasks	Skip task generation, use issue's existing ## Task Checklist

When for issue #[NUMBER] is specified:

1. Fetch issue via gh issue view [NUMBER] --json number,title,body,labels
2. Use issue title + body as the task prompt
3. Extract labels for context (frontend, backend, P1, etc.)

When --use-existing-tasks is specified:

1. Parse existing checklist from ## Task Checklist or ## Acceptance Criteria
2. Skip Step 5 (task generation) - use parsed tasks directly
3. Still run full workflow: exploration, testing questions, workflow options