skills.rest
AuroraWebSoftware
AuroraWebSoftwareOFFICIAL
Explore all skills by this author →
GitHub

openspec-continue-change

Creates the next required Openspec artifact in sequence for change workflows.

41|7|Updated Jun 15, 2022
Search Tags:#workflow#cli#spec#development process#openspec#artifact generation
One-click install
npx skills add https://github.com/AuroraWebSoftware/AAuth --skill openspec-continue-change-aurorawebsoftware
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/AuroraWebSoftware/AAuth/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/AuroraWebSoftware/AAuth --skill openspec-continue-change-aurorawebsoftware

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows users to seamlessly continue their OpenSpec change workflows by creating the next required artifact in a structured process.

Core Features & Use Cases

  • Progressive Artifact Creation: Automatically identifies and creates the next artifact needed in a defined workflow (e.g., proposal, spec, design, tasks).
  • Contextual Awareness: Infers the change to work on from conversation or prompts the user if ambiguous.
  • Status Tracking: Checks the current status of a change and acts based on whether artifacts are ready, blocked, or complete.
  • Use Case: After creating a proposal for a new feature, you can use this Skill to automatically generate the corresponding specification file based on the proposal's capabilities.

Quick Start

Use the openspec-continue-change skill to create the next artifact for the current change.

Frequently Asked Questions about openspec-continue-change

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

FAQPage Schema
How do I continue an OpenSpec change workflow and generate the next artifact?▼

To continue an OpenSpec change workflow, the skill automatically identifies and creates the next required artifact in the sequence, such as a proposal, spec, design, or tasks file, based on the current change status.

What is an OpenSpec spec-driven workflow and when do I need to generate artifacts?▼

An OpenSpec spec-driven workflow is a structured development process where you sequentially generate artifacts like proposals and specifications. You need it to maintain progressive documentation and track feature design status.

Do I need the OpenSpec CLI to create specification files for my development process?▼

Yes, you need the OpenSpec CLI installed. The skill requires the CLI to list available changes, check their current status, and generate the instructions needed to create the next specification artifact.

How does the OpenSpec workflow handle status tracking when multiple changes exist?▼

The OpenSpec workflow checks the status of each change to see if artifacts are ready, blocked, or complete. When multiple changes exist, it prompts the user to select which specific change to work on.

Can I automatically generate a specification from an existing proposal in OpenSpec?▼

Yes, you can automatically generate a specification from an existing proposal. The skill infers the target change from the conversation context and creates the corresponding spec file based on the proposal's capabilities.

Related Skills

Explore More Software Engineering Skills→
wtg42wtg42

openspec-continue-change

Create the next OpenSpec change artifact from CLI status and dependencies.

Community
Intermediate
DanielShuguangDanielShuguang

openspec-continue-change

Create the next OpenSpec artifact in a change workflow.

Community
Advanced
B4sanB4san

openspec-continue-change

Generates the next OpenScript artifact in a predefined workflow using acfm CLI data.

Community
Advanced
tungnguyen10tungnguyen10

openspec-apply-change

Automate implementation of OpenSpec change tasks with progress tracking.

Community
Advanced