openspec-continue-change

Continues an OpenSpec workflow by generating the next required artifact for a selected change.

18|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/igamenovoer/houmao --skill openspec-continue-change-igamenovoer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/igamenovoer/houmao/tree/main/tests/fixtures/plain-agent-def/skills/openspec-continue-change
Command: npx skills add https://github.com/igamenovoer/houmao --skill openspec-continue-change-igamenovoer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you keep moving forward on an OpenSpec change when you’re ready to generate the next required artifact, without manually checking what step comes next.

Core Features & Use Cases

  • Resumes the correct workflow step: Detects whether the selected change is complete, ready to create the next artifact, or blocked.
  • Guided artifact generation: Fetches artifact-specific instructions and uses them to create exactly one artifact in the correct output location.
  • Dependency-aware context: Reads any completed dependencies so the newly created artifact can be consistent with what was already produced.
  • Human-in-the-loop selection: If no change name is provided, it prompts you to choose from the most recently modified changes rather than guessing.

Quick Start

Continue your OpenSpec change by asking the agent to run openspec-continue-change, optionally passing a specific change name you want to 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 generate the next artifact in my OpenSpec workflow?

To generate the next OpenSpec artifact, you run the openspec-continue-change process which checks your current change status and automatically creates exactly one ready artifact based on dependency readiness and workflow order.

What happens if my OpenSpec change is blocked or missing dependencies?

If your OpenSpec change is blocked, the workflow detection step identifies whether the change is complete, ready, or stalled, ensuring no artifact is generated until its required dependency artifacts are completed and readable.

How do I resume an OpenSpec spec workflow from where I left off?

You resume an OpenSpec spec workflow by invoking the continuation command, which calls openspec list and status to evaluate your current artifact state and then generates the exact next required artifact.

Can I choose which OpenSpec change to progress if I have multiple active workflows?

Yes, if no specific change name is provided, the workflow prompts you to select from the most recently modified changes rather than guessing, ensuring you manually select the correct OpenSpec workflow to advance.

How does dependency handling work when generating OpenSpec artifacts?

Dependency handling works by reading any completed dependency artifacts so the newly generated output remains consistent with previously produced OpenSpec artifacts, fetching artifact-specific instructions to guide the generation.

Do I need to manually check which OpenSpec artifact to create next?

No, you do not need to manually check which OpenSpec artifact to create next because the automation determines the current artifact state by evaluating readiness and dependencies to select exactly one ready artifact.