opsx-apply

Implements pending tasks from an OpenSpec change with tests, quality checks, and GitHub issue tracking.

1|Updated Jul 16, 2026
One-click install
npx skills add https://github.com/ConductionNL/buildiq --skill opsx-apply-conductionnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opsx-apply
Source: https://github.com/ConductionNL/buildiq/tree/main/.claude/skills/opsx-apply
Command: npx skills add https://github.com/ConductionNL/buildiq --skill opsx-apply-conductionnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an OpenSpec change proposal into working code requires reading specs, honoring architectural decision records, writing tests, updating task checklists, and keeping GitHub issues in sync — a repetitive, error-prone process when done manually. This Skill automates that implementation loop so each task in a change's tasks.md is executed, verified, and tracked consistently. ## Core Features & Use Cases - Task-driven implementation: Reads the change's status and apply instructions via the openspec CLI, loads ADRs and context files, then implements each pending task in order with tests for new PHP services and Vue components. - Progress synchronization: Updates tasks.md checkboxes, GitHub issue checkboxes, plan.json status, and a single pipeline progress comment after every task. - Quality gate: Runs composer check:strict (PHPCS, PHPMD, Psalm, PHPStan, unit tests) and npm lint/stylelint after implementation, with up to three auto-fix cycles. - Headless CI mode: Supports HYDRA_HEADLESS=1 operation for the Hydra builder container, skipping interactive prompts while keeping all mandatory write steps. - Use Case: A developer runs /opsx-apply add-webhook-support and the Skill implements all six pending tasks — entities, controllers, dispatcher service, tests, and README documentation — then reports passing quality checks. ## Quick Start Ask the assistant to run /opsx-apply on a named OpenSpec change, for example by saying: apply the register-export change and implement its pending tasks.

Frequently Asked Questions about 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 /opsx-apply with an optional change name, such as /opsx-apply add-auth. The skill reads the change status via the openspec CLI, loads ADRs and context files, then implements each pending task in order with tests and documentation updates.

What quality checks run after implementing OpenSpec tasks?▼

The skill runs composer check:strict, which covers PHP lint, PHPCS, PHPMD, Psalm, PHPStan, and unit tests, plus npm lint and stylelint for frontend code. Auto-fixable issues are corrected with phpcbf or ESLint --fix, with a maximum of three fix cycles.

Can opsx-apply run in headless CI mode?▼

Yes. When the prompt says HEADLESS or HYDRA_HEADLESS=1 is set, interactive prompts are skipped and the skill auto-proceeds through all pending tasks. Writes to tasks.md, GitHub issues, plan.json, and the pipeline progress comment remain mandatory in headless mode.

Why does opsx-apply block on the Haiku model?▼

Implementing tasks from OpenSpec changes requires stronger reasoning than Haiku reliably provides, so the skill stops immediately on Haiku and asks you to switch to Sonnet or Opus. This model gate is bypassed only in headless CI mode.

How does opsx-apply update GitHub issue checkboxes?▼

After each task, it reads the tracking_issue number from plan.json, fetches the issue body via GitHub MCP or the gh CLI, flips the matching task line and its indented sub-checkboxes from [ ] to [x], and updates the issue. It never closes the issue.

What happens if implementation hits a blocker mid-change?▼

The skill pauses, reports the issue, and waits for guidance rather than guessing. It shows progress so far, describes the blocker, and offers options such as updating the design artifacts before continuing.