openspec-apply-change

Automating OpenSpec changes involves orchestrating task selection, status checks, and implementation steps across multiple schemas. It reads relevant artifacts like proposals, specs, and tasks to drive context-aware execution with minimal ambiguity and safe fallbacks.

Context-aware execution reads relevant artifacts like proposals, specs, design, and tasks to drive implementation with minimal ambiguity. It ensures changes are scoped minimally and applied consistently across varying artifact contexts during the development workflow.

Applying OpenSpec changes handles blocked, in-progress, and completed states by providing clear guidance and safe fallbacks. It tracks progress dynamically and offers state-specific instructions to prevent errors when encountering blockers during implementation.

Automated change management supports varying artifact contexts and applies across multiple change schemas. It orchestrates implementation steps regardless of schema differences, ensuring consistent application while maintaining progress tracking and context-awareness.

The best way to track progress is through dynamic guidance based on current state, with built-in safeguards for ambiguity or blockers. Progress tracking handles all states from in-progress to all-done, ensuring structured and consistent application of spec changes.

You do not need to manually resolve ambiguity because the process includes built-in safeguards for ambiguity or blockers. It reads relevant artifacts to drive tasks with minimal ambiguity and provides safe fallbacks when blocked states are encountered.