Menú
Use when explaining how Alloy works, how to choose /discuss /plan /execute /verify, or how task artifacts should be maintained.
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
Use only when the user explicitly allows bounded unattended execution of an approved Alloy task.
Use when encountering a bug, regression, failing command, or unexpected behavior before attempting a fix.
Use before planning when requirements are ambiguous, large, user-visible, or likely to cause rework unless decisions are locked.
Use when implementing an approved Alloy plan. Maintains progress.md, enforces TDD/debug discipline, and stops on blocked gates.
Use when a task needs broad source understanding before planning or execution.
Use when turning context or a clear user request into an implementation-ready plan with acceptance criteria, files, commands, gates, risks, and handoff.
| name | alloy-using |
| description | Use when explaining how Alloy works, how to choose /discuss /plan /execute /verify, or how task artifacts should be maintained. |
Alloy v0.1.4 is a command-driven workflow for one developer using OpenCode with two primary agents and disposable subagents.
/discuss and /plan./execute, /verify, and bounded retry loops..alloy/tasks/<task-id>/..alloy/tasks/<task-id>/
context.md # requirements, decisions, constraints, open questions
plan.md # approved or unapproved implementation plan
progress.md # gate checkboxes, iterations, findings, handoff
qa.md # optional QA matrix/report
codebase-map.md # optional source map for broad work
Runtime-only files such as .lock and .alloy/run/ are gitignored.
Use /discuss when the request has product ambiguity, visible behavior choices, acceptance criteria gaps, or non-goal uncertainty.
Use /plan when the goal is known but needs implementation sequencing, files, tests, risks, and handoff.
Use /execute when an approved plan.md exists and Builder should implement.
Use /verify when implementation appears complete and gates must be closed against acceptance criteria.
Use /start-work to resume an existing task.
Use /handoff to produce a continuation summary for a new session.
Common gate lines in progress.md:
## Gate
- [ ] tdd_red
- [ ] debug
- [ ] green
- [ ] review
- [ ] verified
Only include gates that matter for the task. alloy gate check --task-id <id> --json passes when every checkbox under ## Gate is checked.
All Alloy artifacts must include enough detail for a fresh Builder session:
Do not hide important details in chat only.