What problem does it solve? Turning an approved OpenSpec change proposal into working code requires manually tracking tasks, reading the right context files, and keeping progress in sync. This Skill automates that loop by driving the openspec CLI to select a change, load its context, and implement tasks one by one. ## Core Features & Use Cases - Change Selection: Picks a change by name, infers it from conversation context, or lists active changes when ambiguous, with support for registered OpenSpec stores via --store. - Status-Aware Implementation: Reads openspec status and openspec instructions apply output to understand the schema, progress, blocked states, and required context files before editing code. - Task Loop with Progress Tracking: Implements each pending task, marks checkboxes complete in the tasks file, and reports progress as "N/M tasks complete" until done or blocked. - Use Case: After drafting a spec-driven change with proposal, design, and tasks artifacts, run this Skill to work through every task, pause on ambiguities or design issues, and finish with a summary ready for archiving. ## 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 add-auth.
