openspec-bulk-apply-change

Coordinate parallel OpenSpec change application using isolated worktrees and delegated verification.

84|18|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/intent-driven-dev/openspec-schemas --skill openspec-bulk-apply-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-apply-change
Source: https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-bulk-apply-change
Command: npx skills add https://github.com/intent-driven-dev/openspec-schemas --skill openspec-bulk-apply-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of applying multiple active OpenSpec changes concurrently without risking conflicts, inconsistent state, or manual overhead by coordinating isolated worktrees and delegated verification.

Core Features & Use Cases

  • Create isolated worktrees for each candidate change to prevent cross-contamination.
  • Dispatch parallel subagents to apply and verify changes independently.
  • Aggregate results and report readiness for human review without performing merges.
  • Enforce guardrails to prevent auto-merges, auto-archiving, or bulk-merge actions.

Quick Start

Run the bulk apply flow when you have two or more active changes to apply in parallel.

Frequently Asked Questions about openspec-bulk-apply-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply multiple OpenSpec changes in parallel without causing git conflicts?

To apply multiple OpenSpec changes in parallel safely, use isolated git worktrees for each change to prevent cross-contamination, dispatch parallel subagents to apply and verify changes independently, and aggregate results for human review.

What is bulk change management with git worktree isolation?

Bulk change management with git worktree isolation coordinates the simultaneous application of multiple changes by creating separate working directories, dispatching parallel subagents for verification, and reporting aggregate readiness without performing auto-merges.

How to run parallel execution of OpenSpec changes with independent flows?

Run parallel execution of OpenSpec changes by dispatching subagents to apply and verify each change independently within isolated worktrees, enforcing guardrails against auto-merging, and reporting the results for human review.

Does bulk apply perform automatic merging or archiving of OpenSpec changes?

No, bulk apply does not perform automatic merging or archiving. It enforces strict guardrails to prevent auto-merges, auto-archiving, and bulk-merge actions, requiring human review of the aggregated results before proceeding.

When should I use parallel bulk apply for OpenSpec changes?

Use parallel bulk apply for OpenSpec changes when you have two or more active changes to apply concurrently and desire parallel execution with independent flows, preventing cross-contamination through isolated worktrees.

Why does parallel change application require delegated verification?

Parallel change application requires delegated verification to ensure each isolated worktree is independently applied and checked by subagents, preventing inconsistent state and manual overhead while aggregating results for human review.