---
description: Create the next ready artifact based on dependencies.
---
# OpenSpec route: Continue

Use the `openspec` skill for this request.

Workflow action: `continue`
Primary workflow entry: `/openspec <request>`
Explicit action route: `/opsx:continue`

Execution rules:
- Follow the `continue` playbook from the `openspec` skill and its referenced files.
- Read `openspec/config.yaml` if present, then `~/.openspec/.opsx-config.yaml`.
- Use request details already present in the conversation.
- Use inline arguments when available, but confirm ambiguous names or descriptions before mutating files.
- Security-review states are `required`, `recommended`, `waived`, `completed`.
- If config or heuristics indicate a security-sensitive change, create or recommend `security-review.md` after `design` and before `tasks`; if the user waives it, record the waiver in artifacts.
- `spec checkpoint` runs after `design` and before `tasks`; `task checkpoint` runs after `tasks` and before `apply`.
- `execution checkpoint` runs after each top-level task group during `apply`.
- Checkpoint outcomes use `PASS`, `WARN`, `BLOCK` and update existing artifacts instead of creating new review files.
- If the required change name, description, or selection is missing, ask for the minimum clarification needed.
- Read the current change state first and create only the next valid artifact.
- When files are mutated, report changed files, current state, next step, and blockers.