source-command-opsx-apply

Implements tasks from an OpenSpec change with testing, commits, and pull requests.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill source-command-opsx-apply-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-opsx-apply
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/.agents/skills/source-command-opsx-apply
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill source-command-opsx-apply-marcel-carrillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an OpenSpec change proposal into working code requires manually tracking tasks, reading scattered context files, running tests, and managing git branches and pull requests. This Skill automates that entire implementation loop so changes are executed consistently and verifiably. ## Core Features & Use Cases - Guided Task Implementation: Reads the change's tasks via the OpenSpec CLI, implements each pending task, and marks checkboxes complete only with test evidence. - Workflow Orchestration: Enforces workspace isolation on a feature branch, coordinates backend/frontend planning subagents, runs mandatory unit/curl/E2E verification, and writes reports. - Delivery Automation: Commits with Conventional Commits, pushes the branch, opens a pull request with gh pr create, and optionally transitions linked Jira tickets. - Use Case: A developer runs /opsx:apply add-auth and the Skill selects the change, loads its proposal/design/tasks, implements each task with tests, and finishes by opening a PR and moving the Jira ticket to review. ## Quick Start Ask the agent to run /opsx:apply with your change name, for example: implement the OpenSpec change add-auth and open a pull request when done.

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 selects the change, reads its proposal, design, specs, and tasks via the OpenSpec CLI, then implements each pending task and marks it complete only with test evidence.

What happens if I run opsx apply without a change name?▼

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

Does the OpenSpec apply workflow create a pull request automatically?▼

Yes. After all tasks are complete and verified, it commits with a Conventional Commit message, pushes the feature branch, and runs gh pr create using the GitHub CLI, then reports the PR URL.

Can I implement an OpenSpec change directly on the main branch?▼

No. The workflow mandates workspace isolation before editing any file: you must be on a feature branch or worktree such as feature/<change-name>, never on master or main.

What should I do when the apply state is blocked?▼

A blocked state means required artifacts are missing for the change. The workflow shows the blocking message and suggests running the continue command to generate the missing artifacts before applying.

Does the apply workflow integrate with Jira?▼

Yes. If a .jira file with a ticket key exists in the change directory, it transitions the ticket to En curso when implementation starts and to En revisión after the pull request opens, using the Jira REST API or an MCP comment fallback.