openspec-apply-change

Automate OpenSpec change task implementation with TDD and gated reviews.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and structures the manual, error-prone process of implementing tasks from an OpenSpec change by orchestrating CLI inspection, context file reading, test-driven cycles, and task state updates so engineers can make steady, auditable progress.

Core Features & Use Cases

  • Change selection and discovery: Infers or lists available changes, prompts the user when ambiguous, and announces the chosen change and override syntax.
  • Context-aware workflow: Uses openspec status and apply instructions to determine schema, context files, and task progress before making changes.
  • TDD-driven implementation with gated reviews: Enforces a mandatory test-first cycle, then a two-stage review (spec compliance then code quality) before marking tasks complete and committing updates.
  • Progress tracking and safe pausing: Displays current progress, pauses on ambiguity or blockers, and offers clear next steps or options when blocked or complete.
  • Use case: A developer receives an OpenSpec change with seven tasks and uses this Skill to iterate through each task with tests, reviews, and commits until the change is fully implemented or paused for guidance.

Quick Start

Begin implementing the active OpenSpec change by running the skill and following prompts to select the change and start the TDD-driven task loop.

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 implementing tasks from an OpenSpec change?

Automating OpenSpec change tasks involves orchestrating CLI status inspection, reading context files, running test-driven development cycles, and performing gated spec and code reviews to iteratively implement and verify discrete tasks.

What is a spec-driven workflow for managing code changes?

Spec-driven change management uses defined changes containing discrete tasks, requiring iterative implementation, test-first verification, dual-stage reviews, and task state tracking to ensure steady, auditable progress.

How do I enforce test-driven development before completing change tasks?

Enforce test-driven development by applying a mandatory test-first cycle, then executing a two-stage review for spec compliance and code quality before marking tasks complete and committing updates.

Can I pause task automation when encountering ambiguous change instructions?

Yes, the task automation workflow displays current progress, pauses safely on ambiguity or blockers, and offers clear next steps or options when blocked so you can resume or seek guidance.

Do I need the openspec CLI to apply change tasks?

Yes, you need the openspec CLI to generate JSON outputs for status and apply instructions, which the workflow uses to determine schema, context files, and task progress before making changes.

What is the best way to track progress during spec-driven code reviews?

The best way to track progress is by using CLI status outputs to display task completion states, pausing on blockers, and committing updates only after passing both spec compliance and code quality reviews.