openspec-continue
OpenSpec Continue Skill
Use /opsx:continue to create the next artifact in the dependency chain. This builds a change incrementally — one artifact at a time — giving the user control to review and edit before proceeding.
When to Use
- The user wants incremental, step-by-step artifact creation.
- After creating a change with openspec-new and wanting to build artifacts one at a time.
- The user says "continue", "next artifact", "create specs", "create design".
Prerequisites
- An active change exists (created via openspec-new or
/opsx:new).
Workflow
- Query the dependency graph
- The agent runs
openspec status --change <name> --jsonto see which artifacts are done, ready, or blocked.
- The agent runs
More from partme-ai/openspec-skills
openspec-explore
Think through ideas, investigate problems, and clarify requirements before committing to a change using `/opsx:explore`. Use when the user says "explore an idea", "think through this", "investigate options", or wants to brainstorm before creating a formal change.
50openspec-apply
Implement tasks from the change using `/opsx:apply`, working through the task list and checking off items. Use when the user says "implement", "apply the change", "/opsx:apply", or "start coding from tasks".
40openspec-sync
Sync delta specs from a change into main specs using `/opsx:sync`, without archiving the change. Use when the user says "sync specs", "merge specs to main", "/opsx:sync", or needs to update main specs mid-change.
36openspec-schema
Create and manage custom workflow schemas using `openspec schema init/fork/validate/which`. Use when the user says "create a custom workflow", "custom schema", "fork a schema", or wants to define their own artifact types and dependencies.
35openspec-archive
Archive a completed change with `/opsx:archive`, merging delta specs into main specs and preserving the change for history. Use when the user says "archive the change", "finish up", "/opsx:archive", or "mark this change as done".
35openspec-new
Start a new OpenSpec change with `/opsx:new`, creating a change folder with metadata and scaffolding. Use when the user says "start a new change", "new feature", "/opsx:new", or "create an OpenSpec change".
29