Menu
Execute the next pending task from a change proposal
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.
Apply or accept a change proposal and implement its tasks
Create a new change proposal with delta specs and tasks
Accept Spectr change proposals by converting tasks.md to tasks.jsonc without requiring the spectr binary. USE WHEN you're in a sandboxed or restricted execution context and spectr is not available in your path. DO NOT USE WHEN you need a lightweight alternative for task acceptance, but have the spectr binary available. DO NOT USE when you have the spectr binary available.
Accept Spectr change proposals by converting tasks.md to tasks.jsonc without requiring the spectr binary. USE WHEN you're in a sandboxed or restricted execution context and spectr is not available in your path. DO NOT USE WHEN you need a lightweight alternative for task acceptance, but have the spectr binary available. DO NOT USE when you have the spectr binary available.
Based on SOC occupation classification
| name | spectr-next |
| description | Execute the next pending task from a change proposal |
spectr/AGENTS.md and spectr/project.md (located inside
the spectr/ directory—run ls spectr) for project and
Spectr conventions or clarifications.spectr/changes/.tasks.jsonc to find the first task with status: "pending".pending → in_progress → completed.spectr/changes/<id>/proposal.md for proposal details.spectr/changes/<id>/tasks.jsonc for task status and descriptions.spectr/changes/<id>/specs/<capability>/spec.md for delta specs.