Menú
Implement an SDD change from tasks.md — always ask self vs subagents first, then execute only after apply mode is set
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create Spec-Driven Development changes (OpenSpec-style) — multi-project openspec, understanding gate, assigned tasks before coding
Archive a completed SDD change — merge delta specs into main openspec/specs and move change to archive
Run frontend (and FE+BE) apps in Holix Studio: always bind 0.0.0.0, always open Studio preview links in chat, always prefer docker-compose with an nginx reverse proxy that joins frontend and backend. Use when starting Vite/Next/Nuxt/React, SPA+API monorepos, or any web app the user should open in Studio Browser. Invoke via /holix-studio-frontend-backend.
Author and manage Holix agent drop-in extensions so the agent can extend itself without editing Holix core. Use when the user asks to write an extension, add tools, register slash commands, list extensions, disable a broken extension, or self-modify agent capabilities. Invoke via /holix-extensions.
Full Holix sub-agent lifecycle: spawn, monitor, collect results, answer ask_user questions, approve tool confirmations, and delegate to external CLIs (holix launch). Use when the user asks about subagents, /subagent-spawn, delegate_to_subagent, background workers, sub-agent questions, /subagent-reply, holix launch + coder, or running tasks without blocking the main chat. Invoke via /holix-subagents.
Optional guide for web_researcher sub-agent. Use only when the user explicitly asks to delegate web research (e.g. /subagent-spawn web_researcher, "запусти web_researcher").
| name | holix-sdd-apply |
| description | Implement an SDD change from tasks.md — always ask self vs subagents first, then execute only after apply mode is set |
| tags | ["sdd","openspec","apply","implement","subagents","holix"] |
| user-invocable | true |
User says implement / apply / do the change after a proposal exists under openspec/changes/<id>/.
Before any product code:
sdd_status with change_id — must be apply_ready
sdd_request_apply_mode — get the question
Ask the user in chat (show the prompt):
main stays on main)Wait for the answer. Then sdd_set_apply_mode with self | subagents | hybrid
sdd_apply — only proceeds if mode is set; returns plan (task → executor).
For subagents/hybrid it auto-dispatches using the exact assignee from tasks.md (e.g. coder-python).
If mode is missing, sdd_apply fails on purpose. Do not start coding.
sdd_apply only; respect delta specssdd_dispatch job ids — they use tasks.md assignee (custom types). Same type → type-1, type-2, … in parallel. Dispatch budgets max_steps from each task's size (xs/s/m). Then wait_subagent_result; do main tasks yourself.tasks.md — you do not need sdd_check_task for those. Still call sdd_check_task for main tasks and if auto-mark failed.sdd_check_taskholix-sdd-archive / sdd_archive)tasks.md into smaller XS/S items and re-dispatch — do not just raise max_stepstasks.mddelegate_to_subagent with built-in coder when assignee is a custom type (coder-python, …) — that ignores the user's agent