openspec-apply-change

Automate OpenSpec change implementation with guided task execution and progress tracking.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/MaplumeX/Blockwise --skill openspec-apply-change-maplumex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/MaplumeX/Blockwise/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/MaplumeX/Blockwise --skill openspec-apply-change-maplumex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates implementing OpenSpec changes, reducing manual coordination and task-tracking overhead for development teams.

Core Features & Use Cases

  • Guided change application: step-by-step workflow from selecting a change to applying it.
  • Status inspection: query current change status and derive the required artifacts.
  • Context-aware execution: read context files and guide task progression within different schemas (spec-driven, tdd).
  • Progress tracking: updates task completion, handles blocked states, and suggests next steps.
  • Workflow integration: supports actions on a change, interleaving with other tasks and artifact updates.

Quick Start

Run the openspec-apply-change skill to begin applying a change to an OpenSpec project.

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 OpenSpec changes to my project?

You can automate applying OpenSpec changes through a guided workflow that selects changes, reads context, iterates through tasks, and updates progress deterministically while enforcing guardrails to reduce manual coordination overhead.

What is spec-driven change management and how does task automation work?

Spec-driven change management structures modifications into auditable tasks. Task automation queries current status, guides progression across schemas, updates completion states, handles blocked tasks, and suggests next steps to minimize tracking overhead.

Can I use OpenSpec change application with tdd and spec-driven schemas?

Yes, OpenSpec change application supports tdd and spec-driven schemas. It reads context files and guides task progression within either schema, ensuring context-aware execution and deterministic task updates across your selected workflow.

What's the best way to track progress and handle blocked states when implementing OpenSpec changes?

The best way to track progress is querying change status to derive artifacts, then iterating tasks while the system automatically updates completion records, prompts for ambiguity, and suggests next steps for blocked states during OpenSpec implementation.

Why does my OpenSpec change task progression prompt for ambiguity?

Your OpenSpec task progression prompts for ambiguity to enforce guardrails and ensure deterministic, auditable execution. It halts to request clarification when context is unclear, preventing incorrect artifact updates and maintaining workflow integrity.