openspec-continue-change

Generate the next required artifact for an existing OpenSpec change.

139|27|Updated Nov 9, 2014
One-click install
npx skills add https://github.com/nfe/client-nodejs --skill openspec-continue-change-nfe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/nfe/client-nodejs/tree/main/.github/skills/openspec-continue-change
Command: npx skills add https://github.com/nfe/client-nodejs --skill openspec-continue-change-nfe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you keep momentum on an existing OpenSpec change by automatically determining what to do next and generating the next required artifact in the correct order.

Core Features & Use Cases

  • Change Resumption: Lists and lets you select which OpenSpec change to continue when a name is not provided.
  • Workflow State Awareness: Checks current status to determine whether the change is complete, which artifacts are ready, and which are blocked.
  • Artifact Generation Orchestration: Fetches artifact-specific instructions and produces exactly one next artifact using the provided template and dependencies.
  • Progress Reporting: Shows what was created and prompts you to continue until all artifacts are complete.

Quick Start

Ask the assistant to continue an OpenSpec change named "my-change" so it creates the next required artifact and updates your progress.

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 and generate the next required artifact?

Use the openspec-continue-change workflow to automatically select an existing change, check its status, and write the next ready artifact to the specified outputPath while stopping after one artifact.

What is workflow state awareness for spec management?

Workflow state awareness checks current status to determine whether an OpenSpec change is complete, which artifacts are ready for generation, and which are blocked by unresolved dependencies.

How does dependency resolution work when generating OpenSpec artifacts?

Dependency resolution reads required dependency artifacts for context before generating the next file, ensuring the workflow only produces artifacts that are ready and not blocked by missing prerequisites.

Can I resume a spec-driven change without manually tracking status and dependencies?

Yes, you can resume a spec-driven change without manual tracking by using workflow orchestration to automatically list available changes, check status, select the first ready artifact, and generate it.

How do I select which OpenSpec change to continue when multiple exist?

When a name is not provided, the workflow lists existing OpenSpec changes and lets you select which one to continue by generating the next required artifact from its current workflow state.

Does the artifact generation workflow stop after creating one output file?

Yes, the artifact generation workflow stops after creating exactly one output file, reporting what was created and prompting you to continue until all artifacts are complete.