openspec-apply

Implements tasks from an OpenSpec change with progress tracking and codebase exploration.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill openspec-apply-te-quanbzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply
Source: https://github.com/TE-QuanBZhang/skills-pool/tree/main/ai-coding/skills/openspec-apply
Command: npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill openspec-apply-te-quanbzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved OpenSpec change proposal into actual code requires manually tracking tasks, reading scattered context files, and keeping implementation aligned with the design. This Skill automates that execution loop so tasks are implemented, checked off, and verified systematically. ## Core Features & Use Cases - Guided Task Implementation: Reads the change's tasks via the OpenSpec CLI, implements each pending task, and marks checkboxes complete as it goes. - Baseline Health Gate: Verifies the project builds (e.g., Gradle assembleDebug) before editing, preventing wasted iteration on a broken baseline. - CodeGraph-Grounded Exploration: Runs codegraph explore on task keywords to ground code changes in the actual codebase structure and integration points. - Git Branch Workflow: Creates an opsx/<change-name> branch and recommends per-task commits for reviewable, traceable diffs. - Use Case: After proposing an "add-user-auth" change, invoke this Skill to work through all 7 tasks—writing code, updating tests, and checking off tasks—until the change is ready for verification and archive. ## Quick Start Ask the agent to start implementing the tasks for your active OpenSpec change, optionally naming the change explicitly.

Frequently Asked Questions about openspec-apply

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

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

Invoke the apply workflow with an optional change name. It runs openspec status and openspec instructions apply to load context files and the task list, then implements each pending task and marks its checkbox complete in the tasks file.

What happens if I don't specify 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 asks you to pick from the available changes.

Does openspec-apply require the CodeGraph CLI?

No, CodeGraph is an enhancement, not a blocker. It runs codegraph explore to ground implementation in real code structure, but if it returns no useful results the workflow falls back to ripgrep or grep for manual code search.

Why does implementation stop before editing any code?

The baseline health gate fails when the project does not compile, checked via a build such as ./gradlew :app:assembleDebug. You choose to fix the baseline first or force-continue with the risk recorded in the change.

Can it handle conflicts between parallel OpenSpec changes?

Yes. Before the first edit it runs openspec list --json and scans other active changes' proposal and tasks files for overlapping modules. If a conflict is found, it prints an overlap table and asks you to confirm ordering.

What should I do after all tasks are complete?

The workflow suggests running the verify step to compile, lint, and run affected-module unit tests, then archiving the change. Behavior-changing tasks should also have unit tests added or updated before being marked complete.