task-create

Task Create

You create tasks in the project's task management system. The task directory can vary by project.

Resolve TASKS_DIR before running commands:

1. If TASK_MANAGER_TASKS_DIR is set, use that.
2. Else if .claude/tasks exists, use .claude/tasks for backward compatibility.
3. Else if .agents/tasks exists, use .agents/tasks.
4. Else if .kiro/tasks exists, use .kiro/tasks.
5. Else if .idea/agents-tasks exists, use .idea/agents-tasks.
6. Else if TASK_MANAGER_AGENT=codex or you are running in Codex, use .agents/tasks; if TASK_MANAGER_AGENT=kiro-cli or you are running in Kiro, use .kiro/tasks; otherwise use .claude/tasks.

CLI helper

IMPORTANT: Always use a relative path for task-cli.sh — never an absolute path. This ensures permission rules match correctly.

TASKS_DIR="${TASK_MANAGER_TASKS_DIR:-$(case "${TASK_MANAGER_AGENT:-}" in codex) echo .agents/tasks ;; kiro|kiro-cli) echo .kiro/tasks ;; *) echo .claude/tasks ;; esac)}"

# List existing groups and active tasks (includes tracker config)
bash "$TASKS_DIR/task-cli.sh" list

# Create a new group (prints groupId)
bash "$TASKS_DIR/task-cli.sh" add-group "Group Name"

# Create a new task in a group (prints taskId, creates MD file)
bash "$TASKS_DIR/task-cli.sh" add-task <groupId> "Task Name" "Optional description"

Note: list outputs tracker config automatically — no need to call config separately.

If task-cli.sh is not found at $TASKS_DIR/task-cli.sh, copy it from scripts/task-cli.sh.

Input

Arguments via $ARGUMENTS — parsed flexibly. Examples:

• /task-create "Backend API" "Add authentication" "Implement JWT auth flow"
• /task-create "Refactoring" "Extract utils"
• /task-create (no args — ask user interactively)

Steps

1. Resolve TASKS_DIR using the rules above. Check if task-cli.sh exists at $TASKS_DIR/task-cli.sh. If not, look for it at scripts/task-cli.sh and copy it.

2. List existing groups: bash "$TASKS_DIR/task-cli.sh" list