openspec-continue-change

Generate the next artifact for an OpenSpec change in sequence.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/oalansilva/crypto --skill openspec-continue-change-oalansilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/oalansilva/crypto/tree/main/.codex/skills/openspec-continue-change
Command: npx skills add https://github.com/oalansilva/crypto --skill openspec-continue-change-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact.

Core Features & Use Cases

  • Orchestrates the continued progression of an OpenSpec change by generating the next artifact in the defined workflow.
  • Checks current status, fetches artifact instructions, and writes the new artifact to the appropriate path while honoring dependencies and the artifact sequence.
  • Useful for automating incremental spec development and ensuring consistent traceability across changes.

Quick Start

Tell me which OpenSpec change to continue, or ask me to select from the most recently modified changes, and I will generate the next artifact according to the active workflow.

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 artifact in the workflow?

To continue an OpenSpec change, the skill checks the current status, fetches artifact instructions, and writes the next artifact to the specified path while respecting dependencies. You simply specify the change or ask it to select from recently modified ones.

What is the process for automating incremental spec development with OpenSpec?

Automating incremental spec development involves orchestrating the continued progression of an OpenSpec change by generating the next artifact in the defined workflow. This ensures consistent traceability across changes by honoring the artifact sequence.

How does artifact generation respect dependencies when evolving a spec-driven change?

Artifact generation respects dependencies by checking the current status via openspec status and fetching guidelines with openspec instructions before writing. This ensures the new artifact honors the required sequence and dependencies.

Do I need to manually specify the artifact path when continuing an OpenSpec change?

No, you do not need to manually specify the artifact path. The skill fetches instructions and automatically writes the new artifact to the appropriate path defined by the active OpenSpec workflow.

What happens if there are multiple recently modified OpenSpec changes to continue?

If there are multiple recently modified OpenSpec changes, the skill can select from the most recently modified ones. It will prompt you when necessary to identify the specific change you want to evolve.