openspec-apply-change

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

4|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-apply-change-januarylabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/JanuaryLabs/deepagents/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-apply-change-januarylabs

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill streamlines implementing concrete development tasks described in an OpenSpec change by reading CLI-provided instructions and context files, applying focused code changes, and updating task state until the change is complete or paused for blockers.

## Core Features & Use Cases

  • Change selection and guidance: Infers or prompts for the change to work on and announces the selected change with override instructions.
  • CLI-driven workflow: Uses openspec status and openspec instructions apply to discover schema, contextFiles, progress, and dynamic instructions.
  • Iterative implementation loop: Reads context files, implements pending tasks with minimal scoped changes, updates task checkboxes, and reports progress; pauses when tasks are ambiguous or blocked.
  • Guardrails and safety: Requires reading contextFiles before acting, prompts on ambiguity, suggests artifact updates when design issues appear, and avoids guessing on unclear requirements.

### Quick Start Run openspec instructions apply for the chosen change and follow the CLI JSON output to read context files, implement the next pending task, and mark it complete.

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 OpenSpec change tasks from the CLI?

To implement OpenSpec change tasks, run openspec instructions apply for the chosen change and follow the CLI JSON output to read context files, implement the next pending task, and mark it complete.

What is spec-driven change management in OpenSpec?

Spec-driven change management in OpenSpec is a workflow that uses the openspec CLI to discover schema, contextFiles, and dynamic instructions to iteratively implement pending development tasks with minimal scoped changes.

Do I need to install any dependencies to apply OpenSpec changes?

Yes, applying OpenSpec changes requires the openspec CLI installed in your environment to parse JSON output for context files, progress tracking, and dynamic apply instructions.

How does the OpenSpec workflow handle ambiguous or blocked implementation tasks?

The OpenSpec workflow pauses implementation when tasks are ambiguous or blocked, prompting for clarification and suggesting artifact updates if design issues appear to avoid guessing on unclear requirements.

Can I use OpenSpec to update task state and progress automatically?

Yes, OpenSpec updates task state automatically by reading context files, implementing pending tasks with focused code changes, updating task checkboxes, and reporting progress until the change is complete.

What are the limitations of using OpenSpec for task implementation?

OpenSpec task implementation requires reading contextFiles before acting and will not proceed on unclear requirements, meaning it pauses for blockers and prompts on ambiguity rather than guessing.