source-command-opsx-apply

Implements tasks from an OpenSpec change using CLI-driven status and instructions.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill source-command-opsx-apply-jonathanlin768
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-opsx-apply
Source: https://github.com/jonathanlin768/CS2Match-Nakama/tree/main/.agents/skills/source-command-opsx-apply
Command: npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill source-command-opsx-apply-jonathanlin768

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork of turning an OpenSpec change proposal into actual code by walking through each pending task, reading the right context files, and tracking progress automatically. ## Core Features & Use Cases - Change Selection: Resolves which OpenSpec change to work on from user input, conversation context, or an interactive picker backed by openspec list --json. - Status-Aware Execution: Reads openspec status and openspec instructions apply output to understand the schema, progress, and context files before editing code. - Task Loop with Guardrails: Implements tasks one by one, checks them off in the tasks file, and pauses on ambiguity, design issues, or blockers instead of guessing. - Use Case: After drafting a spec-driven change for a new API endpoint, run the apply command to have each task implemented sequentially with progress reported as "N/M tasks complete". ## Quick Start Ask the assistant to apply the OpenSpec change named add-auth and implement its remaining tasks.

Frequently Asked Questions about source-command-opsx-apply

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

FAQPage Schema
How do I implement tasks from an OpenSpec change?

Run the apply command with a change name, such as /opsx:apply add-auth. The workflow fetches status and apply instructions from the openspec CLI, reads the listed context files, then implements each pending task and marks it complete.

What happens if I don't specify a change name?

The skill infers the change from conversation context or auto-selects when only one active change exists. If ambiguous, it runs openspec list --json and asks you to pick from the available changes.

Can I apply a change before all artifacts are complete?

Yes, the workflow is fluid and can run whenever tasks exist, even mid-planning. If required artifacts are missing the status reports a blocked state and suggests continuing artifact creation first.

Why does apply stop in workspace-planning mode?

When status reports actionContext mode workspace-planning with empty allowedEditRoots, full workspace edits are unsupported. Linked repos are treated as read-only context and you must choose an affected area through an explicit implementation workflow.

What should I do when implementation reveals a design problem?

The skill pauses and suggests updating the change artifacts rather than forcing a bad implementation. You can revise the proposal, specs, or design, then resume applying the remaining tasks.