openspec-apply-change

Convert OpenSpec changes into tracked implementation task workflows.

6|2|Updated Feb 10, 2026

Search Tags:#task management #implementation #json #progress tracking #openspec #context files #schema-driven workflow

Ready to run

npx skills add https://github.com/LingoJack/jcli --skill openspec-apply-change-lingojack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/LingoJack/jcli/tree/main/.github/skills/openspec-apply-change
Command: npx skills add https://github.com/LingoJack/jcli --skill openspec-apply-change-lingojack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec CLI.

What problem does it solve?

It helps you translate an OpenSpec change into concrete, step-by-step implementation work, keeping task status, progress, and required context aligned with the change’s schema.

Core Features & Use Cases

Select the correct OpenSpec change: Infer from conversation context, auto-select when unambiguous, or prompt you by listing available changes.
Use schema-specific apply instructions: Fetch dynamic implementation instructions via the OpenSpec CLI, including the right context files to read.
Execute tasks safely and traceably: Loop through pending tasks, apply minimal scoped changes, mark tasks complete, and pause when blocked or unclear.

Quick Start

Run the skill with the change name if you know it, otherwise let it infer the change from your conversation so it starts applying tasks automatically.

Frequently Asked Questions about openspec-apply-change

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

FAQPage Schema

How do I start implementing an OpenSpec change and tracking task progress?▼

To start implementing an OpenSpec change, the skill infers the target change from your context, calls the openspec CLI for schema-aware instructions, and iterates through the returned task list to track progress. It auto-selects the change when unambiguous or prompts you to choose.

How does OpenSpec schema-driven workflow handle context files during implementation?▼

OpenSpec schema-driven workflow handles context files by fetching dynamic apply instructions via the CLI in JSON mode and reading the specific contextFiles returned. This ensures task execution remains aligned with the change's required schema and minimal scoped changes.

Do I need the openspec CLI to apply changes and execute tasks?▼

Yes, you need the openspec CLI installed to apply changes and execute tasks. The skill requires calling openspec status and openspec instructions apply in JSON mode to retrieve the task list and context files needed for the implementation workflow.

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

When a task is blocked or ambiguous during OpenSpec implementation, the workflow pauses execution. Instead of forcing a potentially incorrect change, it halts the iteration loop to prevent unsafe modifications until the ambiguity is resolved.

Can I resume partial progress on an active OpenSpec change?▼

Yes, you can resume partial progress on an active OpenSpec change. The skill applies when you need to start, continue, or complete work, looping through pending tasks, marking completed ones, and safely pausing on blocked items.

How do I select the correct OpenSpec change if multiple are available?▼

To select the correct OpenSpec change, the skill first attempts to infer it from your conversation context. If multiple active changes exist and the target is ambiguous, it lists available changes and prompts you to select the intended one.