What problem does it solve? Turning an OpenSpec change proposal into working code requires tracking task progress, reading the right context artifacts, and updating task checklists consistently, which is error-prone when done manually. ## Core Features & Use Cases - Change Selection: Resolves the target change from user input, conversation context, or by listing active changes when ambiguous. - Status-Driven Implementation: Reads schema, progress, and apply instructions from the openspec CLI, then works through pending tasks one by one. - Guardrailed Execution: Pauses on unclear tasks, design issues, or scope creep instead of silently narrowing specified behavior. - Use Case: After drafting a spec-driven change with proposal, design, and tasks artifacts, run this skill to implement each task, mark checkboxes complete, and finish with an archive-ready change. ## Quick Start Ask the assistant to implement the tasks for your OpenSpec change, for example by saying "apply the add-auth change".