What problem does it solve? Turning an approved OpenSpec change proposal into working code requires manually tracking tasks, reading the right spec artifacts, and keeping progress in sync. This Skill automates that loop by driving the openspec CLI to select a change, load its context files, implement each task, and mark completion. ## Core Features & Use Cases - Change selection and status tracking: Resolves the target change from user input or conversation context, then reports schema, progress, and remaining tasks via openspec status and openspec instructions apply. - Guided task implementation loop: Reads all context files (proposal, specs, design, tasks), implements each pending task with minimal scoped edits, and flips - [ ] to - [x] as work completes. - Guardrails and pause handling: Stops on ambiguity, design issues, scope creep, or errors, presenting options instead of guessing; supports multi-store setups via --store <id>. - Use Case: After drafting a spec-driven change with tasks for a new API endpoint, invoke this Skill to work through all seven tasks, updating the tasks file and receiving a completion summary with an archive suggestion. ## Quick Start Ask the assistant to implement the tasks for your OpenSpec change, for example by saying "apply the add-auth change" or running /opsx-apply with the change name.
