openspec-continue-change

Generate the next OpenSpec artifact from current change status.

1|Updated Jun 18, 2025
One-click install
npx skills add https://github.com/knopki/dotfiles --skill openspec-continue-change-knopki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/knopki/dotfiles/tree/main/home/private_dot_config/opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/knopki/dotfiles --skill openspec-continue-change-knopki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users seamlessly continue their work on OpenSpec changes by automating the creation of the next required artifact in a workflow, ensuring progress and adherence to defined processes.

Core Features & Use Cases

  • Workflow Progression: Automatically identifies and creates the next artifact based on the current status of an OpenSpec change.
  • Contextual Artifact Generation: Reads dependencies and applies schema-specific rules and templates to generate artifacts like proposals, specs, designs, and tasks.
  • Use Case: After creating a proposal for a new feature, use this Skill to automatically generate the corresponding specification file based on the capabilities outlined in the proposal.

Quick Start

Use the openspec-continue-change skill to create the next artifact for the 'user-authentication' 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 automate artifact generation for an OpenSpec change workflow?

Automate OpenSpec artifact generation by parsing the current change status, identifying the next ready artifact, and generating it using schema-specific rules, templates, and context dependencies.

What is the process to continue OpenSpec changes and create the next artifact?

The process to continue OpenSpec changes involves parsing current workflow status, identifying the next ready artifact, and generating files like proposals, specs, designs, or tasks using provided instructions and templates.

How do I generate specifications from a proposal in a spec-driven development process?

Generate specifications from a proposal by applying schema-specific rules and templates to read dependencies and contextualize the outlined capabilities, automatically producing the corresponding specification artifact.

Does OpenSpec change management support schema-driven workflows for designs and tasks?

Yes, OpenSpec change management supports spec-driven schemas for proposals, specs, designs, and tasks, automatically progressing through defined workflows to identify and create the next ready artifact.

What is the best way to ensure adherence to defined development processes when creating OpenSpec artifacts?

Ensure adherence to development processes by automating artifact creation through contextual generation, which reads dependencies and applies schema-specific templates to maintain consistent workflow progression.

Can I use scripts to automatically progress through OpenSpec change workflows?

Yes, you can use scripts to automatically progress through OpenSpec change workflows by parsing the current status and generating the next required artifact based on defined schemas and contextual dependencies.