openspec-apply-change

Guide users through applying OpenSpec changes with task tracking.

21|10|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/zaloclaw/zaloclaw-infra --skill openspec-apply-change-zaloclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/zaloclaw/zaloclaw-infra/tree/main/.github/skills/openspec-apply-change
Command: npx skills add https://github.com/zaloclaw/zaloclaw-infra --skill openspec-apply-change-zaloclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing OpenSpec changes can be complex and error-prone. This skill guides users through selecting an active change, inspecting its status, retrieving apply instructions, reading required context, and iterating through tasks until all steps are complete, reducing missteps and manual coordination.

Core Features & Use Cases

  • Guided, multi-step workflow to apply OpenSpec changes across schemas (spec-driven, tasks, design, tests, and implementation).
  • Reads and uses context files to inform progress, and updates task checkboxes as tasks are completed.
  • Handles edge states like blocked changes and all_done completion, and pauses for clarification or when blockers are encountered.
  • Supports interleaving artifact updates and ongoing changes, enabling fluid, artifact-driven collaboration.

Quick Start

To begin, specify a change name or let the system infer it, then follow prompts to apply and implement tasks.

Frequently Asked Questions about openspec-apply-change

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

FAQPage Schema
How do I apply an OpenSpec change across spec-driven workflows?

To apply an OpenSpec change, you select an active change, inspect its status, and iterate through tasks by reading context files and updating task checkboxes as each step completes.

What is the process for managing task tracking during a spec-driven change?

Managing spec-driven changes involves reading required context files before work begins, executing tasks sequentially, and updating task checkboxes to reflect completion status across artifacts like proposals, specs, and implementations.

How does OpenSpec handle blocked changes or when all tasks are done?

OpenSpec handles blocked changes by pausing for clarification or when blockers are encountered, and recognizes an all_done state when all task execution steps are fully complete.

Can I interleave artifact updates while executing OpenSpec tasks?

Yes, you can interleave artifact updates and ongoing changes during OpenSpec task execution, enabling fluid and artifact-driven collaboration across your workflow.

Do I need to manually specify a change name to start the OpenSpec workflow?

No, you do not need to manually specify a change name; you can provide one to begin, or the system can infer it before guiding you through the apply and implementation process.