openspec-apply-change

Automate applying OpenSpec changes with task status updates and progress checks.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/memorysaver/agentpit-gg --skill openspec-apply-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/memorysaver/agentpit-gg/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/memorysaver/agentpit-gg --skill openspec-apply-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates applying an OpenSpec change, orchestrating status checks, context loading, and task-tracking across a multi-step workflow to ensure consistent progress.

Core Features & Use Cases

  • Change selection and application: determine the target change, announce the active change, and support overrides.
  • Progress guidance: read status and schema to guide implementation across tasks and artifacts.
  • Context loading: read context files (proposal/specs/design/tasks) to drive tasks and decisions.
  • Task progression: update task checkboxes as tasks are completed and provide clear completion or pause states.
  • Use Case: when a change spans multiple tasks, this Skill keeps execution aligned with the OpenSpec plan and surfaces blockers early.

Quick Start

Steps to begin:

  • Check the current status of a change: openspec status --change "<change-name>" --json
  • Retrieve apply instructions: openspec instructions apply --change "<change-name>" --json
  • Start implementing tasks as guided, updating task checkpoints after each task completes.

Frequently Asked Questions about openspec-apply-change

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

FAQPage Schema
How do I automate applying changes across multiple tasks in a structured workflow?

Automate change application by using OpenSpec to select a target change, read context files, update task checkboxes as work completes, and track progression through a multi-step workflow. This ensures consistent status alignment and surfaces blockers early across all tasks in the change.

What's the best way to manage task progression when implementing a large change?

Track task progression by reading the current status, loading context from proposal and design files, implementing guided tasks, and updating checkpoints after each completes. This structured iteration keeps execution aligned with your plan and provides clear completion or pause states.

How do I check if a change is ready to apply and what steps should I follow?

Query change readiness using `openspec status --change` to review progress, then retrieve apply instructions with `openspec instructions apply --change` in JSON format. Follow the guided tasks, updating checkboxes as you complete each step until the change reaches completion or a pause state.

Can I use this workflow if my change spans multiple artifacts and task files?

Yes. The Skill reads context files including proposals, specs, design docs, and task files to drive multi-artifact changes. It enforces a structured iteration workflow that keeps all task statuses synchronized and reports clear states across the full change scope.

What happens if a change is ambiguous during application?

The Skill prompts you to clarify the ambiguous change before proceeding, ensuring you select the correct target change and supporting overrides. This prevents misaligned execution and lets you confirm the active change before implementation begins.