What problem does it solve? Turning an approved OpenSpec change proposal into working code requires tracking task status, reading the right context artifacts, and updating checklists consistently, which is error-prone when done manually. ## Core Features & Use Cases - Change Selection and Status Tracking: Selects a change by name or context, then parses openspec status JSON to understand the 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 work finishes. - Blocked-State and Pause Handling: Detects blocked or all-done states, surfaces design issues or scope creep, and pauses for user guidance instead of guessing. - Use Case: After drafting an OpenSpec change for a new authentication feature, run this Skill to work through every task in the tasks file, updating code and checkboxes until the change is 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".