Menu
Validate a scaffy template syntax and structure. Use --strict to also flag missing transforms, anchors, IDs.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-scaffy-validate |
| description | Validate a scaffy template syntax and structure. Use --strict to also flag missing transforms, anchors, IDs. |
ls .doey/scaffy/templates/*.scaffy 2>/dev/null || echo "(none)"Parse a .scaffy template and report syntax or structural problems before applying it.
doey-scaffy validate <template>.scaffy [flags]
--strict — apply strict checks (variables must have explicit Transforms, INSERT/REPLACE need IDs, guarded ops need REASON, anchor targets must be non-empty)--json — emit a JSON validation report ({valid, errors[], warnings[]})--cwd <dir> — working directory# Plain syntax check
doey-scaffy validate .doey/scaffy/templates/handler.scaffy
# Strict mode with JSON output for CI
doey-scaffy validate --strict --json .doey/scaffy/templates/handler.scaffy
valid: false); warnings are reported but pass--strict in CI to enforce template hygiene/doey-scaffy-audit afterward to also check the working tree for staleness