openspec-bulk-apply-change

name	openspec-bulk-apply-change
description	Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
license	MIT
compatibility	Requires git, OpenSpec CLI, and Codex subagents.
metadata	{"author":"openspec","version":"1.0","generatedBy":"1.3.1"}

Project context preflight before workflow actions: before this skill takes a workflow action, follow the project-constitution skill. Read root CONSTITUTION.md when present, enforce relevant project rules, stop on material conflicts, and follow the strict missing-constitution bootstrap/diagnostic policy. For architecture-sensitive work, also read ARCHITECTURE.md, adr/README.md, and relevant in-force adr/*.md. Read .secrets.local.env only when the current workflow actually needs a listed external system, and never reveal secret values.

OpenSpec Bulk Apply

Apply multiple active OpenSpec changes by creating isolated worktrees, dispatching delegated apply flows in parallel subagents, running verification in each flow, and reporting back without merging or archiving.

REQUIRED SUB-SKILL: Use openspec-git-discipline before any apply or worktree workflow.

When to Use

• More than one active OpenSpec change exists
• /opsx:bulk-apply was invoked without an explicit single-change target
• The user wants multiple changes applied in parallel
• The user asks to apply all active OpenSpec changes

Do not use bulk mode when only one candidate change remains. Stop and tell the user to use /opsx:apply <change> instead.

Steps

1. Get candidate changes

   Run:

   openspec list --json
   

   • If command input included change names, limit analysis to those changes.
   • If fewer than 2 active candidate changes remain, stop and tell the user to use /opsx:apply <change>.
   • Do not ask the user to choose one change when 2 or more candidates remain and the request is clearly bulk apply.

2. Run git discipline checks

   For each candidate change, verify apply is allowed before creating worktrees:

   • Run git status --short.
   • Verify openspec/changes/<change>/ has no uncommitted proposal files.
   • Verify the proposal change exists on main before applying from any branch or worktree.

   If any candidate fails the gate, exclude it from execution and report the reason. If fewer than 2 executable candidates remain, stop and report that bulk apply is not appropriate.

3. Collect change context

   For each executable candidate change:

   openspec status --change "<name>" --json
   openspec instructions apply --change "<name>" --json
   

   Then:

   • Read all listed contextFiles.
   • Read the tasks artifact and summarize pending work.
   • Note the implementation scope needed by the delegated apply flow.
   • Exclude blocked or all-done changes from execution and include them in the final report.

4. Parent goal-guidance preflight before orchestration side effects

   Run this preflight after executable changes are known, blocked/all-done changes have been excluded, and context is available, but before creating worktrees or dispatching subagents.

   Stop without a bulk goal when:

   • Fewer than two executable changes remain. Report skipped/excluded changes and suggest /opsx:apply <change> for the single remaining change.
   • A planning-artifact gate failed for the requested run and leaves fewer than two executable changes.
   • Orchestration is blocked before worktree creation by missing credentials, missing repository access, unavailable external systems, or contradictory artifacts that need user decisions.

   Skip parent goal generation and continue orchestration when:

Quick Reference

Situation	Action
2+ active candidates	Bulk apply in isolated worktrees
Explicit list of 2+ changes	Bulk apply only those changes
1 candidate	Stop and use /opsx:apply <change>
Proposal not on main	Exclude or stop before apply
Already inside an active goal for same changes	Skip parent goal and continue
User explicitly says no goal	Continue without parent goal
Blocked or all-done change	Skip execution and report status
Subagent finishes apply	Require /opsx:verify <change> before review-ready
User asks to merge/archive	Stop and require explicit follow-up approval

Common Mistakes

Mistake	Fix
Asking user to pick one change for a bulk request	Keep all executable candidates when 2+ remain
Creating worktrees before goal preflight	Generate the parent /goal prompt first unless goal guidance is active or bypassed
Creating a nested parent goal	When already inside a covering active goal, continue directly
Running apply in the parent workspace	Dispatch one subagent per worktree
Processing changes sequentially	Dispatch independent apply flows in parallel
Reporting ready after apply only	Require /opsx:verify <change> first
Treating verify as permission to merge	Report only; merge needs explicit approval
Archiving after verify	Never archive during bulk apply

Guardrails

• Do not auto-merge.
• Do not auto-archive.
• Do not auto-create goals; print a copy-paste parent /goal prompt and stop when goal guidance is triggered.
• Do not create nested goals when the run is already covered by an active Codex Goal.
• Do not bulk-apply when only one candidate change remains.
• Do not perform apply work in the parent agent; use subagents only.
• Do not run bulk apply in the main workspace; use isolated worktrees only.
• Keep .worktrees/ as the default worktree root unless the user specifies another location.
• Require /opsx:verify in every delegated apply flow before reporting a change as review-ready.
• Preserve OpenSpec git discipline: apply only changes whose proposal state has reached main.