ワンクリックで
doey-instant-task
Quick task creation without planning — create and dispatch immediately. Usage: /doey-instant-task <goal>
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Quick task creation without planning — create and dispatch immediately. Usage: /doey-instant-task <goal>
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Plan-first task creation — research, breakdown, risk analysis, then create tasks from approved plan. Usage: /doey-planned-task <goal>
Request a respawn of the current worker pane. Use when you need to "respawn me", "restart myself", "fresh context", or "reset my pane". Writes an atomic respawn request that kills the current Claude process and relaunches with a fresh context.
Discover scaffolding patterns in this project — structural fingerprints, accretion files, and refactoring patterns from git history. Returns candidates worth turning into templates.
Spawn the doey-scaffy MCP server so workers can drive the Scaffy template engine via tool calls. Loaded automatically when a task needs scaffy_run / scaffy_validate / scaffy_list / scaffy_audit / scaffy_discover / scaffy_new / scaffy_fmt or any scaffy:// resource.
Create a new scaffy template from existing files (--from-files) or interactively. Outputs to .doey/scaffy/templates/<name>.scaffy.
Manage persistent project tasks — list, add, transition, show, subtasks, decisions, notes. Tasks stored in .doey/tasks/ (survives reboot). Use when you need to "show tasks", "add a task", "mark a task done", "what are we working on", or "create a task".
| name | doey-instant-task |
| description | Quick task creation without planning — create and dispatch immediately. Usage: /doey-instant-task <goal> |
doey task list 2>/dev/null || echo "No tasks"Never suggest /doey-worktree, branch creation, or worktree flow when creating or describing the task. All commits go to the session's starting branch (typically main). If — and only if — the user's literal goal text contains the word "worktree", you may surface /doey-worktree as the explicit opt-in path.
Create and dispatch a task immediately from a natural-language goal. No planning step. Goal from ARGUMENTS (if empty, use AskUserQuestion to ask, then stop).
For complex multi-step work, suggest /doey-planned-task instead.
Determine type and priority from the goal:
Infer from keywords: "fix"/"bug"/"broken" → bugfix, "add"/"new"/"create" → feature, "clean"/"simplify" → refactor, "investigate"/"explore" → research.
TASK_ID=$(doey task create --title "TITLE" --type "TYPE" --description "DESCRIPTION")
echo "Created task #${TASK_ID}"
For tasks with obvious sub-parts, add subtasks:
doey task subtask add --task-id "$TASK_ID" --description "Subtask title"
Send message to Taskmaster for routing:
RD=$(tmux show-environment DOEY_RUNTIME 2>/dev/null | cut -d= -f2-)
TASKMASTER_PANE=$(grep '^TASKMASTER_PANE=' "${RD}/session.env" 2>/dev/null | cut -d= -f2-)
TASKMASTER_PANE="${TASKMASTER_PANE:-1.0}"
doey msg send --to "${SESSION_NAME}:${TASKMASTER_PANE}" --from "${DOEY_PANE_ID}" \
--subject "new_task" \
--body "TASK_ID: ${TASK_ID}
TITLE: ${TASK_TITLE}
TYPE: ${TASK_TYPE:-feature}
PRIORITY: ${TASK_PRIORITY:-P2}
Instant task — ready for immediate dispatch."
doey msg trigger --pane "${SESSION_NAME}:${TASKMASTER_PANE}"
Report: task ID, title, type, priority, dispatch status. Keep it brief — this is the fast path.
doey task create — never duplicate/doey-planned-task instead