What problem does it solve? Turning an OpenSpec change proposal into working code requires tracking task status, reading the right context files, and updating checkboxes consistently, which is error-prone when done manually. ## Core Features & Use Cases - Change Selection: Automatically infers the active change from context or lists available changes via openspec list --json when ambiguous. - Status-Aware Implementation: Reads schema, progress, and context files from openspec status and openspec instructions apply before writing any code. - Task Loop with Guardrails: Implements tasks one by one, marks them complete in the tasks file, and pauses on ambiguity, blockers, or scope creep instead of guessing. - Use Case: After drafting a spec-driven change with proposal, design, and tasks artifacts, run this skill to work through all pending tasks and finish with a progress summary and archive suggestion. ## Quick Start Ask the assistant to implement the tasks for your OpenSpec change, optionally naming the change, for example by saying implement the add-auth change.
