openspec-apply-change-ai-kit

Apply OpenSpec change instructions to implement pending tasks.

Updated May 11, 2026
One-click install
npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill openspec-apply-change-ai-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change-ai-kit
Source: https://github.com/ducthang-hub/nw-ai-kit/tree/main/.agents/skills/openspec-apply-change-ai-kit
Command: npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill openspec-apply-change-ai-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly implement the concrete tasks defined by an OpenSpec change, while keeping you aligned with the schema, required context files, and the current task state.

Core Features & Use Cases

  • Change-aware task orchestration: Infers or selects the correct OpenSpec change, reads status, and applies the right instructions for the active workflow schema.
  • Context-driven implementation: Reads the context files returned by the OpenSpec CLI so you implement against the actual artifacts the change references.
  • State-safe execution and progress updates: Handles blocked and all-done states, pauses on unclear tasks or errors, and marks each task complete to track progress.

Quick Start

Implement a selected OpenSpec change by running: openspec apply --change "My Change Name".

Frequently Asked Questions about openspec-apply-change-ai-kit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement pending tasks from an OpenSpec change in my codebase?

To implement OpenSpec tasks, use the openspec apply command with a specific change name. The workflow reads status, applies instructions, and iterates through pending tasks with minimal scoped edits to update your codebase.

What is a schema-driven workflow for applying codebase updates?

A schema-driven workflow applies codebase updates by reading spec-driven artifacts like proposals, specs, designs, and tasks. It uses OpenSpec CLI instructions to ensure implementation adheres to required context files and structured schemas.

How does progress tracking work when executing OpenSpec task instructions?

Progress tracking works by updating task completion state after each scoped edit. The workflow handles blocked, all_done, and pause-on-unclear conditions, ensuring state-safe execution while marking tasks complete throughout the implementation lifecycle.

Can I resume an interrupted task implementation if an OpenSpec change has errors?

Yes, you can resume interrupted task implementation. The workflow supports starting, resuming, or continuing implementation, and automatically pauses on unclear tasks or errors to prevent invalid codebase updates until the issue resolves.

Do I need to manually read context files before applying OpenSpec changes?

No, you do not need to manually read context files. The workflow automatically reads the contextFiles returned by the OpenSpec CLI, allowing you to implement changes directly against the actual artifacts the change references.

What happens when all tasks in an OpenSpec change are completed?

When all tasks in an OpenSpec change are completed, the workflow handles the all_done state. It verifies that all pending tasks have been implemented with minimal scoped edits and updates the final task completion state.