openspec-apply-change

Implement OpenSpec change tasks using CLI apply instructions and context files.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/martinsson/checkin-automation --skill openspec-apply-change-martinsson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/martinsson/checkin-automation/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/martinsson/checkin-automation --skill openspec-apply-change-martinsson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the manual, error-prone process of implementing tasks defined by an OpenSpec change by guiding the agent through selecting a change, retrieving apply instructions, reading repository context files, and updating task artifacts until completion or pause.

Core Features & Use Cases

  • Change selection & discovery: Infer or list available changes and let the user pick when ambiguous.
  • Instruction-driven implementation: Use openspec CLI output to determine schema, context files, progress, and dynamic apply instructions before making code changes.
  • Task loop with guardrails: Iterate through pending tasks, make minimal scoped changes, mark tasks complete, and pause for clarifications or blockers.
  • Use Case: Implement remaining tasks for a spec-driven change such as updating design artifacts, applying code changes, and marking tasks complete after verifying context files and instructions.

Quick Start

Use the openspec-apply-change skill to implement pending tasks for the change named "add-login" by fetching the apply instructions and following the listed context files and 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 implement tasks from an OpenSpec change using the CLI?

To implement OpenSpec tasks, use the openspec CLI to produce JSON status and apply instructions. The agent reads context files, makes minimal scoped changes, and updates the tasks artifact to mark completions until the change is finished.

What is spec-driven change management and when do I need it?

Spec-driven change management uses the openspec CLI to define schema, context files, and tasks for code changes. You need it when automating structured workflow implementations to reduce manual errors and ensure context-aware updates.

How do I apply dynamic instructions and context files to update code changes?

Applying dynamic instructions involves running the openspec CLI to fetch apply instructions, reading the listed repository context files, executing the specified tasks, and updating the tasks artifact to track progress.

Does OpenSpec change implementation require specific CLI outputs to function?

Yes, OpenSpec change implementation requires the openspec CLI to output JSON status and apply instructions. It also needs access to repository context files listed by the CLI and the ability to update tasks artifacts.

What happens when a task is ambiguous or blocked during change implementation?

When tasks are ambiguous, the workflow lists available changes for user selection. If blocked during implementation, the task loop pauses for clarifications before proceeding with further code changes.

Why are my OpenSpec change tasks not progressing through the implementation loop?

OpenSpec tasks fail to progress if the openspec CLI cannot produce JSON status, apply instructions are missing, repository context files are inaccessible, or the tasks artifact cannot be updated to mark completions.