What problem does it solve? Turning an OpenSpec change proposal into working code requires tracking task status, reading the right context artifacts, and updating checkboxes consistently, which is error-prone when done manually. ## Core Features & Use Cases - Change Selection and Status Tracking: Selects a change by name or inference, then parses openspec status and openspec instructions apply JSON output to understand schema, progress, and remaining tasks. - Guided Task Implementation Loop: Reads context files (proposal, specs, design, tasks), implements each pending task, and marks checkboxes complete as it goes. - Blocked and Paused State Handling: Detects blocked or all-done states, pauses on ambiguity or errors, and reports progress with structured output. - Use Case: After drafting an OpenSpec change for a new feature, run this skill to work through every task in the tasks file until the change is fully implemented and ready to archive. ## Quick Start Ask the assistant to implement the tasks from your OpenSpec change, for example by saying "apply the add-auth change". ## Quick Start Use this skill to implement all pending tasks from the OpenSpec change named add-auth.