openspec-apply-change

Implements tasks defined in an OpenSpec change for spec-driven applications.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/augentic/vectis --skill openspec-apply-change-augentic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/augentic/vectis/tree/main/.cursor/skills/openspec-apply-change
Command: npx skills add https://github.com/augentic/vectis --skill openspec-apply-change-augentic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the implementation of tasks defined within an OpenSpec change, streamlining the development workflow for spec-driven applications.

Core Features & Use Cases

  • Task Automation: Executes predefined tasks from an OpenSpec change, reducing manual effort.
  • Workflow Management: Tracks progress, handles blocked states, and guides the user through implementation steps.
  • Use Case: After an OpenSpec change has been proposed and artifacts generated, use this Skill to automatically implement the defined tasks, check the code, and report on progress.

Quick Start

Use the openspec-apply-change skill to implement the tasks for the 'create-my-app' change.

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 development tasks for spec-driven applications?

To automate spec-driven development tasks, implement predefined tasks from an OpenSpec change. The skill executes these tasks automatically, reducing manual effort and tracking progress throughout the workflow.

What is OpenSpec change task implementation?

OpenSpec change task implementation is the process of executing predefined development tasks defined within an OpenSpec change. It dynamically fetches instructions and context files to automate the workflow for spec-driven applications.

How do I handle blocked states when automating code generation workflows?

When automating code generation workflows, the system handles blocked states by tracking progress and guiding the user through necessary implementation steps. It provides continuous progress updates to ensure task completion.

Does this task automation approach work with various schemas?

Yes, this task automation approach supports various schemas by dynamically fetching the required instructions and context files. This ensures the spec-driven implementation adapts to different project structures.

When should I use automated task implementation in my development workflow?

Use automated task implementation after an OpenSpec change has been proposed and artifacts are generated. It automatically implements the defined tasks, checks the code, and reports on progress to streamline development.

What are the limitations of automating spec-driven development tasks?

Automating spec-driven development tasks requires a proposed OpenSpec change with generated artifacts beforehand. Task automation depends on these predefined instructions and context files to execute the implementation process successfully.