Openspec Continue Change

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

3,306 stars 317 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add rpamis/comet --skill openspec-continue-change
Manual install
git clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/eval/local/skills/benchmarks/dependency/openspec/openspec-continue-change ~/.claude/skills/openspec-continue-change

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

Continue working on a change by creating the next artifact.

**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

**Steps**

1. **If no change name provided, prompt for selection**

   Run `openspec list --json` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.

   Present the top 3-4 most recently modified changes as options, showing:
   - Change name
   - Schema (from `schema` field if present, otherwise "spec-driven")
   - Status (e.g., "0/5 tasks", "complete", "no tasks")
   - How recently it was modified (from `lastModified` field)

   Mark the most recently modified change as "(Recommended)" since it's likely what the user wants to continue.

   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.

2. **Check current status**
   ```bash
   openspec status --change "<name>" --json
   ```
   Parse the JSON to understand current state. The response includes:
   - `schemaName`: The workflow schema being used (e.g., "spec-driven")
   - `artifacts`: Array of artifacts with their status ("done", "ready", "blocked")
   - `isComplete`: Boolean indicating if all artifacts are complete

3. **Act based on status**:

   ---

   **If all artifacts are complete (`isComplete: true`)**:
   - Congratulate the user
Read the full skill on GitHub

Details

Skill name
openspec-continue-change
Repository
rpamis/comet
Path
eval/local/skills/benchmarks/dependency/openspec/openspec-continue-change/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Openspec Continue Change skill do?

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

How do I install the Openspec Continue Change skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill openspec-continue-change. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Openspec Continue Change popular?

It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.

Related skills

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.