665,000+ skills indexed

zthxxxCOMMUNITY

Explore all skills by this author →

Verified:𝕏@zthxxxxx GitHub

openspec-continue-change

Create the next OpenSpec change artifact based on schema rules.

Updated Apr 4, 2026

Search Tags:#workflow #documentation #openspec #spec management #artifact creation

One-click install

npx skills add https://github.com/zthxxx/hams --skill openspec-continue-change-zthxxx

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/zthxxx/hams/tree/main/.agents/skills/openspec-continue-change
Command: npx skills add https://github.com/zthxxx/hams --skill openspec-continue-change-zthxxx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill assists users in managing and progressing their OpenSpec changes by creating subsequent artifacts, ensuring an organized and efficient workflow.

Core Features & Use Cases

Change Workflow Management: Enables continuation of work on an existing OpenSpec change by creating the next artifact.
Artifact Selection & Creation: Guides users to select the relevant change, checks current status, and generates missing or next required artifacts based on schema rules.
Use Case: A team working collaboratively on a specification can use this Skill to iteratively develop proposals, specifications, designs, and tasks, maintaining version control and consistency.

Quick Start

Use the skill to pick up from your latest OpenSpec change and generate the next artifact needed to proceed.

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 prompts you to select the relevant change, checks current status, and automatically generates the next required artifact based on schema rules.

What is the best way to manage iterative spec management for collaborative proposals?▼

Iterative spec management is handled by guiding artifact creation for proposals, specifications, designs, and tasks, maintaining version control and consistency for teams practicing structured documentation processes.

How do I check current progress and create missing artifacts in OpenSpec?▼

Checking current progress and creating missing artifacts is done by selecting an existing change, allowing the skill to evaluate status against schema rules and generate subsequent required documentation.

Do I need a specific environment setup to automate OpenSpec artifact creation?▼

Automating OpenSpec artifact creation requires an existing change workflow with established schema rules, ensuring the skill can properly evaluate progress and generate subsequent documentation artifacts.

Can I use this skill to maintain version control for structured design documentation?▼

Maintaining version control for structured design documentation is supported by iteratively developing specifications and designs, ensuring consistency across collaborative team workflows with minimal manual effort.

When should I not use automated artifact creation for OpenSpec changes?▼

Automated artifact creation for OpenSpec changes is not suitable when schema rules are undefined or when a structured documentation process is not established, as the skill relies on existing progress checks.

Related Skills

Explore More Software Engineering Skills→

openspec-continue-change

Generate OpenSpec change artifacts to continue workflow progression.

project-init

Generate standardized project artifacts from a design specification.

blueprint-sdd-step01-intake

Automate initial scoping and documentation for SDD software projects.

openspec-continue-change

Identify and generate the next schema-compliant artifact in OpenSpec change workflows.