メニュー
Compile a natural-language goal into a structured task package (.task + .json). Usage: /doey-create-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-create-task |
| description | Compile a natural-language goal into a structured task package (.task + .json). Usage: /doey-create-task <goal> |
doey task list 2>/dev/null || echo "No tasks"Prefer /doey-planned-task for multi-step work and /doey-instant-task for simple tasks. This skill creates raw task files without planning — use it as a fallback only.
Compile a natural-language goal into a task package. Goal from ARGUMENTS (if empty, ask and stop).
/doey-task add "title", stopTYPE: [feature|bugfix|refactor|research|audit|docs|infrastructure]
INTENT: [what + why] | BRIDGE: [current → desired state]
HYPOTHESES: H1 [approach, confidence] | H2 [alternative, confidence]
CONSTRAINTS | SUCCESS CRITERIA | DELIVERABLES
DISPATCH: [standard|phased] + team assignment
Use phased if goal mentions phases, sequential deps, or "staged".
TASK_ID=$(doey task create --title "TITLE" --type "TYPE" --description "DESCRIPTION")
echo "Created task #${TASK_ID}"
Update task with compiled fields.
Success criteria format: Each criterion must describe the expected result/state, not a command to run. Criteria should be independently verifiable by automation.
doey task update --id "$TASK_ID" --field "intent" --value "..."
doey task update --id "$TASK_ID" --field "hypotheses" --value "H1: ..."
doey task update --id "$TASK_ID" --field "constraints" --value "..."
doey task update --id "$TASK_ID" --field "success_criteria" --value "..."
doey task update --id "$TASK_ID" --field "deliverables" --value "..."
doey task update --id "$TASK_ID" --field "dispatch_plan" --value "standard"
doey task update --id "$TASK_ID" --field "TASK_DISPATCH_MODE" --value "phased"
doey task update --id "$TASK_ID" --field "TASK_CURRENT_PHASE" --value "0"
doey task update --id "$TASK_ID" --field "TASK_TOTAL_PHASES" --value "$TOTAL_PHASES"
ID, title, type, intent, hypotheses, dispatch plan, paths. Phased: phase count/titles.
Use doey task create — never duplicate. /doey-task add for simple tasks. One clarifying question max.