execute-openspec-change

Automating OpenSpec change execution involves orchestrating design validation, planning, worktree management, subagent execution, code review, testing, and merging through an automated trigger pattern, eliminating manual handoffs across these fragmented stages.

Git worktree-based isolation provides predictable, parallel change execution for OpenSpec changes by separating environments, ensuring state persistence and safety checks prevent cross-branch contamination during subagent execution and automated testing.

Yes, OpenSpec change orchestration integrates automatically with Superpowers skills for design brainstorming, plan generation, and code review, handling state persistence and rollback support throughout the automated workflow.

When conflict detection triggers during OpenSpec change execution, the orchestration workflow provides rollback options and user prompts to safely resolve the issue, ensuring state management persists the execution state for recovery.

No specific external dependencies are required to orchestrate OpenSpec proposals with subagents; the skill handles execution modes, progress tracking, and state management natively while integrating with Superpowers skills.