What problem does it solve? Turning an OpenSpec change proposal into actual code requires manually tracking which tasks are done, which artifacts provide context, and what to do next. This Skill automates that loop by reading the change's tasks and context files via the openspec CLI, implementing each pending task, and marking progress as it goes. ## Core Features & Use Cases - Change Selection: Infers the target change from conversation context, auto-selects when only one active change exists, or prompts the user to pick from openspec list output. - Status-Aware Implementation: Parses openspec status and openspec instructions apply JSON to understand the schema, progress, and context files before writing any code. - Task Loop with Guardrails: Implements tasks one by one, checks off - [x] boxes in the tasks file, and pauses on ambiguity, design issues, or errors instead of guessing. - Use Case: A developer has an approved OpenSpec change with 7 tasks. They invoke the skill, which reads the proposal, specs, design, and tasks files, then implements each task sequentially while reporting progress until all tasks are complete and ready to archive. ## Quick Start Ask the assistant to start implementing the tasks for your current OpenSpec change, optionally naming the change explicitly.
