openspec-apply-change

Implement OpenSpec change tasks with status checks and progress updates.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill openspec-apply-change-alex1980alex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill openspec-apply-change-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you execute an OpenSpec change by turning a defined set of tasks into concrete implementation work with clear progress tracking and status checks.

Core Features & Use Cases

  • Change selection: Identify the correct change from conversation context or by listing available changes when the request is ambiguous.
  • Status-driven workflow: Inspect the current schema, task state, and required context files before making changes.
  • Iterative implementation: Work through tasks one by one, update task checkboxes as each item is completed, and pause when blockers or unclear requirements appear.
  • Use case: A developer asks to continue a partially completed specification update, and this Skill loads the relevant artifacts, reports progress, and carries the work forward safely.

Quick Start

Use this skill to implement the tasks for an OpenSpec change by naming the change or letting it infer the correct one from context.

Frequently Asked Questions about openspec-apply-change

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

FAQPage Schema
How do I implement tasks from an OpenSpec change sequentially?

Implement OpenSpec changes by selecting the active change, checking its status via the OpenSpec CLI, loading apply instructions, and completing tasks sequentially while updating progress checkboxes and handling blockers immediately.

What is spec-driven development change management workflow?

Spec-driven change management turns a defined set of specification tasks into concrete implementation work with clear progress tracking, status checks, and iterative task completion across schema-specific artifacts and context files.

How do I continue a partially completed OpenSpec change implementation?

To continue a partially completed OpenSpec change, the workflow loads relevant artifacts, inspects the current schema and task state, reports existing progress, and safely carries the implementation forward from the last completed task.

How does progress tracking work during OpenSpec task implementation?

Progress tracking during OpenSpec task implementation works by inspecting the current task state, working through tasks one by one, updating task checkboxes as each item is completed, and pausing when blockers or unclear requirements appear.

What happens when there are ambiguous OpenSpec change requests?

When an OpenSpec change request is ambiguous, the workflow identifies the correct change from conversation context or lists available changes for selection before loading apply instructions and proceeding with implementation.

Do I need the OpenSpec CLI to apply changes to schema-specific artifacts?

Yes, applying OpenSpec changes to schema-specific artifacts requires the OpenSpec CLI for status checks, loading apply instructions, and retrieving required context files before making any modifications.