openspec-continue-change

Creates the next artifact for an OpenSpec change using the openspec CLI.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/trutoman/Conjuros --skill openspec-continue-change-trutoman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/trutoman/Conjuros/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/trutoman/Conjuros --skill openspec-continue-change-trutoman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Continuing a spec-driven change requires knowing which artifact comes next, what its template and rules are, and where to write it. This Skill automates that progression by querying the openspec CLI for change status and generating exactly one artifact per invocation. ## Core Features & Use Cases - Change Selection: Infers the active change from context or lists recent changes with status and modification time when ambiguous. - Status-Driven Progression: Parses openspec status JSON to find the first ready artifact and fetch its instructions, template, and dependencies. - Guarded Artifact Creation: Re-reads dependency files from disk, applies context and rules as constraints without copying them into output, and verifies the file exists after writing. - Use Case: You have an OpenSpec change with a completed proposal and want the next artifact (such as design or tasks) generated correctly — invoke this Skill and it creates exactly that one artifact, then reports progress. ## Quick Start Ask the assistant to continue your OpenSpec change, optionally naming the change, and it will create the next ready artifact.

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?

Invoke the continue workflow with an optional change name. It runs openspec status to find the first artifact marked ready, fetches its instructions and template, creates that single artifact, and reports updated progress.

How does the skill pick which change to work on?

It uses a provided name, infers from conversation context, or auto-selects when only one active change exists. If ambiguous, it lists the most recently modified changes from openspec list --json and asks you to choose.

Does this skill require the openspec CLI installed?

Yes, the skill shells out to openspec commands such as status, instructions, and list, so the openspec CLI must be available. Its frontmatter declares compatibility requiring the openspec CLI.

Can it create multiple artifacts in one run?

No, the guardrails explicitly limit each invocation to creating one artifact, the first one with ready status. You invoke it again to create subsequent artifacts in the schema-defined sequence.

What happens when all artifacts in a change are complete?

When openspec status reports isComplete true, the skill stops without creating anything, shows the final status and schema used, and suggests implementing or archiving the change.