openspec-apply

Execute approved OpenSpec change tasks step-by-step with test-tdd verification.

Updated Oct 26, 2025
One-click install
npx skills add https://github.com/discountedcookie/10x-mapmaster --skill openspec-apply
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply
Source: https://github.com/discountedcookie/10x-mapmaster/tree/main/.opencode/skills/openspec-apply
Command: npx skills add https://github.com/discountedcookie/10x-mapmaster --skill openspec-apply

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill implements approved OpenSpec changes by following the tasks.md precisely, including test-driven steps.

Core Features & Use Cases

  • Strict task execution: Do not add or skip tasks; follow the approved plan.
  • Test-driven implementation: Each code task loads test-tdd and verifies changes.
  • Progress reporting: Documents completed tasks and next steps.

Quick Start

Load this skill after OpenSpec approval and execute the listed tasks exactly.

Frequently Asked Questions about openspec-apply

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

FAQPage Schema
How do I implement approved OpenSpec changes step-by-step?

Load openspec-apply after OpenSpec approval, then execute each task listed in tasks.md sequentially without additions or skips. The Skill loads test-tdd for verification, runs each implementation step, and validates results against prescribed tests before committing changes.

What does test-driven implementation mean in OpenSpec workflows?

Test-driven implementation means each code task integrates test-tdd verification: you write or modify code, run the prescribed test commands immediately, and confirm the results pass before moving to the next task. This ensures changes match the approved specification exactly.

Can I skip tasks or reorder steps when applying an OpenSpec change?

No. The Skill enforces phase-driven execution and prohibits task additions or skips. You must follow the exact sequence and specifications in tasks.md to maintain the integrity of the approved change and ensure all verification steps pass.

How do I know if my OpenSpec implementation is complete?

The Skill documents each completed task and reports next steps. Implementation is complete when all pending tasks in tasks.md execute successfully and test-tdd verification commands confirm the results match the approved specification.

What happens if a task fails during OpenSpec implementation?

When test-tdd verification fails, the Skill halts execution and reports the failure without proceeding. You must resolve the failed task against the approved specification before continuing to maintain exact compliance with the OpenSpec change.