skills.rest
Soju06
Soju06COMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Creates the next OpenSpec artifact from parsed status and templates via the openspec CLI.

2.6k|399|Updated Jan 7, 2026
Search Tags:#workflow#development#schema#cli#openspec#artifact generation
One-click install
npx skills add https://github.com/Soju06/codex-lb --skill openspec-continue-change-soju06
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/Soju06/codex-lb/tree/main/.agents/skills/openspec-continue-change
Command: npx skills add https://github.com/Soju06/codex-lb --skill openspec-continue-change-soju06

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users continue working on their OpenSpec changes by automating the creation of the next required artifact in a defined workflow.

Core Features & Use Cases

  • Workflow Progression: Automatically identifies and creates the next artifact (e.g., proposal, spec, design, task) based on the current status of an OpenSpec change.
  • Contextual Generation: Uses schema-specific instructions, templates, and dependency information to generate accurate artifacts.
  • 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 capabilities outlined in the proposal.

Quick Start

Use the openspec-continue-change skill to create the next artifact for the 'add-user-auth' 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 automatically generate the next artifact in an OpenSpec workflow?▼

To automatically generate the next artifact in an OpenSpec workflow, use a skill that parses your current change status and applies schema-specific templates to create the required proposal, spec, or design file.

What is the best way to progress a spec-driven schema change after creating a proposal?▼

Progressing a spec-driven schema change involves reading the current proposal status to identify dependencies, then applying custom workflow instructions to generate the subsequent specification document.

Do I need the openspec CLI to continue custom workflow artifact generation?▼

Yes, you need the openspec CLI installed to perform status checks and execute artifact generation when continuing custom workflows and spec-driven schema changes.

How does contextual artifact generation work with schema-specific instructions?▼

Contextual artifact generation works by parsing dependency information and schema-specific templates from your current workflow status to ensure the next generated file accurately reflects the required capabilities.

Can I use custom workflow templates for spec-driven development?▼

Yes, you can use custom workflow templates for spec-driven development by defining schema-specific instructions that the artifact generation process parses to create subsequent project files.

Related Skills

Explore More Software Engineering Skills→
arestivoarestivo

openspec-continue-change

Generate the next OpenSpec change artifact from CLI status and instructions.

Community
Advanced
benjaminkittbenjaminkitt

openspec-verify-change

Validate implementations against openspec change artifacts for completeness, correctness, and coherence.

Community
Advanced
MeetTechnologyMeetTechnology

openspec-continue-change

Automate OpenSpec change progression by generating the next artifact via CLI.

Community
Advanced
tatargabortatargabor
30

openspec-continue-change

Create the next OpenSpec artifact from CLI JSON outputs and templates.

Community
Advanced