Opsx Bulk Apply

---
description: Apply multiple OpenSpec changes concurrently in isolated worktrees
argument-hint: optional change names
---

Project constitution preflight:
- Before this workflow takes action, use skill `project-constitution` to read and enforce root `CONSTITUTION.md`. For architecture-sensitive work, also read `ARCHITECTURE.md`, `adr/README.md`, and relevant in-force `adr/*.md`.
- If the constitution is missing, follow the bootstrap-safe/diagnostic rules from that skill; otherwise stop unless the user gives an explicit one-time override.
- Do not read `.secrets.local.env` unless this workflow actually needs a listed external system, and never reveal secret values.

Use skill `openspec-bulk-apply-change`.

Rules:
- Use only when two or more active changes are eligible.
- Run git discipline checks before creating worktrees.
- Run goal-guidance preflight after executable changes are known and before creating worktrees or dispatching subagents.
- Create one isolated worktree per executed change under `.worktrees/<change>` unless the user specifies another root.
- Dispatch one Codex subagent per worktree when subagents are available.
- Each subflow runs `/opsx:apply <change>` and `/opsx:verify <change>`.
- Report results without merging or archiving.

Goal-guidance preflight:
- If fewer than two executable changes remain, stop and suggest `/opsx:apply <change>`; do not generate a bulk goal.
- If the current session is already inside an active Codex Goal whose objective covers the same changes, state that parent goal generation is skipped and continue orchestration.
- If the user explicitly asks to continue without a goal, states "no goal", or otherwise clearly bypasses goal guidance, state the bypass and continue orchestration.
- Otherwise, for two or more executable changes, present one copy-paste parent `/goal` prompt and stop before creating worktrees or dispatching subagents.

Generated bulk goal shape: