一键导入
openspec-continue-change
Use when working with OpenSpec in Hermes: create the next ready artifact based on the schema dependency graph.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when working with OpenSpec in Hermes: create the next ready artifact based on the schema dependency graph.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when working with OpenSpec in Hermes: implement tasks from an OpenSpec change and keep task checkboxes updated.
Use when working with OpenSpec in Hermes: archive one completed change, optionally syncing specs first.
Use when working with OpenSpec in Hermes: archive multiple completed changes and handle spec conflicts.
Use when working with OpenSpec in Hermes: manage OpenSpec CLI setup, validation, browsing, workspaces, context stores, initiatives, and shell integration.
Use when working with OpenSpec in Hermes: customize OpenSpec project config, rules, templates, and schemas.
Use when working with OpenSpec in Hermes: run the expanded OpenSpec scaffold, fast-forward, apply, verify, and optional archive workflow end to end.
| name | openspec-continue-change |
| description | Use when working with OpenSpec in Hermes: create the next ready artifact based on the schema dependency graph. |
| version | 1.0.0 |
| author | TheSmuks + Hermes Agent |
| license | MIT |
| platforms | ["windows","macos","linux"] |
| metadata | {"hermes":{"category":"software-development","tags":["openspec","sdd","spec-driven-development","hermes"],"homepage":"https://github.com/Fission-AI/openspec"}} |
Use this for OpenSpec's /opsx:continue workflow.
openspec --version. If missing, install with npm install -g @fission-ai/openspec@latest.openspec init --tools none unless the user also wants other AI-tool integrations. Hermes uses these skills, not OpenSpec-generated slash commands.--json where available: openspec list --json, openspec status --change <id> --json, openspec instructions <artifact> --change <id> --json, openspec validate --all --json.openspec validate <change> or openspec validate --all.openspec list --json if omitted.openspec status --change <name> --json.ready. If multiple are ready, choose dependency order from the schema unless user choice matters.openspec instructions <artifact> --change <name> --json.openspec validate <name>.Do not fast-forward through multiple artifacts. Use openspec-ff-change for that.