菜单
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.
用 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.
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".
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-mcp |
| description | 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. |
| mcp_servers | [{"name":"doey-scaffy","command":"doey-scaffy","args":"serve --stdio","env":{}}] |
When this skill is loaded, Doey's skill-embedded MCP lifecycle (task #499)
parses the mcp_servers block above, generates a per-pane .mcp.json
config in $DOEY_RUNTIME/mcp/, and launches the Claude instance with
--mcp-config <path>. The doey-scaffy binary is spawned as a stdio
MCP server for the duration of the worker's session.
Load this skill from any worker that needs to run, validate, list, or
generate .scaffy templates. The MCP tools below appear in the worker's
tool palette as mcp__doey-scaffy__<tool-name> and the resources as
mcp__doey-scaffy__<resource-uri>.
No manual setup is required — the skill spawns the server, and Doey's team-despawn cleanup tears down the MCP process and config when the team is killed.
scaffy_run — Apply a .scaffy template to the working tree (the 7-stage execution pipeline).scaffy_validate — Parse a template and (optionally) run strict validation checks.scaffy_list — List the templates available in .doey/scaffy/templates/.scaffy_audit — Report which templates are stale, broken, or missing canonical formatting.scaffy_discover — Mine the working tree and git history for scaffolding patterns: structural directory shapes, accretion (injection) files, and refactoring co-creation pairs.scaffy_new — Scaffold a new template stub, optionally seeded from existing files.scaffy_fmt — Format a template to canonical form (idempotent Parse + Serialize).scaffy://registry — The .doey/scaffy/REGISTRY.md catalog, served as text/markdown.scaffy://audit — JSON report of registry health (stale, broken, drift).scaffy://template/{name} — The raw .scaffy source of a single template.scaffy://templates — A JSON array of RegistryEntry objects (one per discoverable template).doey-scaffy binary must be installed at ~/.local/bin/doey-scaffy.
It is built from tui/cmd/scaffy/ by _build_all_go_binaries in
shell/doey-go-helpers.sh and installed alongside the rest of Doey's
Go binaries. If the binary is missing, run doey reinstall (or
doey doctor to confirm) before loading this skill.doey-scaffy MCP process; there is no
cross-team sharing of in-memory registry state.