メニュー
Create a new scaffy template from existing files (--from-files) or interactively. Outputs to .doey/scaffy/templates/<name>.scaffy.
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.
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".
Quick inline clarification loop — a few targeted AskUserQuestion rounds to sharpen a vague goal before task creation. Use when you need to "clarify", "interview the user", "sharpen a vague goal", or resolve ambiguity without spawning a full /deep-interview window.
| name | doey-scaffy-new |
| description | Create a new scaffy template from existing files (--from-files) or interactively. Outputs to .doey/scaffy/templates/<name>.scaffy. |
ls .doey/scaffy/templates/ 2>/dev/null || echo "(none — will be created)"Create a new .scaffy template, either as an empty stub, from a set of existing files, or by walking an interactive prompt.
doey-scaffy new <name> [flags]
--from-files FILE... — seed the template with CREATE blocks for each file (variables inferred from repeated identifiers in the files' contents)--domain <name> — set the template's DOMAIN field (e.g. web, cli, infra)--interactive — walk a guided prompt for description, domain, and tags--force — overwrite an existing template with the same name--output <path> — destination .scaffy path (default: .doey/scaffy/templates/<name>.scaffy)# Empty stub
doey-scaffy new handler
# Seeded from existing handler + test pair
doey-scaffy new handler --from-files src/handler.go src/handler_test.go --domain web
# Guided prompt
doey-scaffy new handler --interactive
.doey/scaffy/templates/<name>.scaffy--force/doey-scaffy-validate --strict after creating to catch missing fields/doey-scaffy-discover to find candidate file sets first