openspec-apply-change

Apply approved tasks from tasks.md through SPARK-workflow debugging, review, and verification gates.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Miss-PinkElf/Multi-Agent --skill openspec-apply-change-miss-pinkelf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/Miss-PinkElf/Multi-Agent/tree/main/.claude/skills/spark-workflow/skills/openspec-apply-change
Command: npx skills add https://github.com/Miss-PinkElf/Multi-Agent --skill openspec-apply-change-miss-pinkelf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spark-workflow teams need a safe, auditable mechanism to implement only approved tasks while enforcing debugging, review, and verification gates.

Core Features & Use Cases

  • Enforces task boundaries by applying only approved changes from tasks.md
  • Provides debugging checkpoints, review gates, and verifiable evidence per task
  • Useful for regulated teams or collaborative SPARK-workflow environments to maintain traceability

Quick Start

Apply the approved tasks from tasks.md within SPARK-workflow and validate each task through debugging, review, and verification gates.

Frequently Asked Questions about openspec-apply-change

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

FAQPage Schema
How do I apply only approved tasks from a SPARK-workflow tasks.md file?

To apply approved tasks from tasks.md, the skill reads approved artifacts and validates each task against acceptance criteria while enforcing strict boundaries. It ensures only authorized changes are implemented across sequential, parallel, or subagent task modes.

What is the best way to enforce debugging and review gates during task automation?

Enforcing debugging and review gates during task automation requires routing failures to appropriate gating mechanisms. The process validates each task against acceptance criteria and collects verifiable evidence per task before proceeding.

Can I use this to maintain traceability for code review in regulated environments?

Yes, you can maintain traceability for code review in regulated environments. The process provides debugging checkpoints, review gates, and verifiable evidence per task to ensure auditable task implementation.

Does this work with sequential, parallel, and subagent task modes?

Yes, it works with sequential, parallel, and subagent task modes. The application scopes task execution across these modes within tasks.md while maintaining strict boundaries and collecting evidence for each approved change.

Why does task application route failures to gating skills during verification?

Task application routes failures to gating skills during verification to enforce debugging, review, and verification gates. When validation against acceptance criteria fails, the system ensures the failure is handled by the appropriate gate before proceeding.