openspec-apply-change

Automate OpenSpec change task implementation and progress tracking via the openspec CLI.

41|7|Updated Jun 15, 2022
One-click install
npx skills add https://github.com/AuroraWebSoftware/AAuth --skill openspec-apply-change-aurorawebsoftware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/AuroraWebSoftware/AAuth/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/AuroraWebSoftware/AAuth --skill openspec-apply-change-aurorawebsoftware

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the implementation of tasks defined within an OpenSpec change, streamlining the development workflow and ensuring tasks are completed systematically.

Core Features & Use Cases

  • Task Automation: Executes predefined tasks from an OpenSpec change, updating progress automatically.
  • Contextual Awareness: Infers or prompts for the correct change if not explicitly provided.
  • Status Tracking: Monitors task completion and provides clear progress updates.
  • Use Case: When a new feature specification is defined in OpenSpec, this Skill can be used to automatically implement the associated development tasks, such as writing code, updating documentation, or creating tests.

Quick Start

Use the openspec-apply-change skill to implement the tasks for the change named 'new-user-authentication'.

Frequently Asked Questions about openspec-apply-change

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

FAQPage Schema
How do I automate task implementation from a spec-driven development workflow?

Spec-driven task implementation is automated by fetching change details and instructions via the openspec CLI, then systematically executing tasks while tracking progress and updating artifacts automatically.

How does spec-driven task automation track development progress?

Spec-driven task automation tracks progress by monitoring task completion states through the openspec CLI, providing clear updates as predefined development tasks are executed and artifacts are modified.

Do I need the openspec CLI to apply change tasks?

Yes, the openspec CLI is required to apply change tasks, as it fetches the necessary change details and instructions and manages the underlying task states for the workflow execution.

What is the best way to implement an OpenSpec change without specifying its name?

If a change name is not explicitly provided, the workflow implementation infers or prompts for the correct OpenSpec change, ensuring the right task set is targeted for execution.

Can I use spec-driven automation for writing code and updating documentation?

Yes, spec-driven automation executes predefined tasks from an OpenSpec change to handle development actions like writing code, updating documentation, or creating tests systematically.

When should I not use automated task execution for spec-driven changes?

Automated task execution should be avoided when a development scenario lacks systematic task definitions or when changes require manual intervention outside the predefined OpenSpec workflow constraints.