openspec-apply-change

Implement OpenSpec change tasks by running CLI commands and updating task checkboxes.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-apply-change-jankneumann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/openspec-apply-change
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-apply-change-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing tasks from an OpenSpec change often requires running CLI commands, reading multiple context files, tracking progress, and carefully updating task artifacts; this Skill coordinates those steps so implementation proceeds reliably and stops when blocked or unclear.

Core Features & Use Cases

  • Change selection & discovery: infer a change from conversation context, auto-select if only one active change exists, or prompt the user with available changes.
  • Context-aware implementation loop: run openspec status and openspec instructions apply, read contextFiles, present progress, implement pending tasks, and update task checkboxes incrementally.
  • Guardrails and error handling: detect blocked or completed states, pause for unclear tasks or design issues, and suggest artifact updates or archival when appropriate.
  • Use case: Iterate through a spec-driven change's tasks file to make small, focused code changes, marking each task complete and reporting session progress.

Quick Start

Ask the assistant to implement the next pending tasks for a named OpenSpec change or ask it to infer the active change from the conversation 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 file iteratively?

To implement OpenSpec change tasks, run openspec status and openspec instructions apply, read context files, make focused code changes, and update task checkboxes incrementally until all pending tasks are complete.

What is the best way to track progress when applying spec-driven code changes?

Tracking spec-driven code changes involves updating task checkboxes in artifacts incrementally after each code modification, allowing you to pause for blockers and report session progress reliably.

Does openspec-apply-change require the openspec CLI to function?

Yes, openspec-apply-change requires the openspec CLI to run status checks, fetch apply instructions via JSON output parsing, and manage the spec-driven workflow.

How do I auto-select an active OpenSpec change from conversation context?

The workflow infers the active OpenSpec change from conversation context, auto-selects it if only one active change exists, or prompts you with available changes to choose from.

What happens when a task is blocked or unclear during OpenSpec implementation?

When an OpenSpec implementation task is blocked or unclear, the workflow pauses execution, detects design issues or completed states, and suggests artifact updates or archival when appropriate.

When should I not use an automated task implementation loop for OpenSpec changes?

You should avoid automated task implementation loops when tasks lack clear context files, require complex design decisions outside the spec, or when the openspec CLI cannot parse JSON output for the current change.