| name | openspec-ship-change |
| description | Use when working with OpenSpec in Hermes: take an existing OpenSpec change from current state through remaining planning, apply, verify, and archive. |
| 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","workflow"],"homepage":"https://github.com/Fission-AI/openspec"}} |
openspec-ship-change
Use this for an already-created OpenSpec change that should be finished automatically from wherever it currently is.
Flow:
detect state -> fill missing planning -> apply remaining tasks -> verify -> archive when safe
Ground rules
- Work from the user's project root. If unknown, inspect the current directory first.
- Ensure OpenSpec exists with
openspec --version. If missing, install it with npm install -g @fission-ai/openspec@latest.
- If
openspec/ is missing, initialize with openspec init --tools none.
- Use OpenSpec CLI state as source of truth:
openspec list --json, openspec status --change <id> --json, openspec instructions <artifact> --change <id> --json, openspec validate <id>.
- Do not stop at a plan. Create artifacts, implement code, run checks, update task checkboxes, and report real command output.
- Ask only when a real decision changes the work. Otherwise choose the recommended default and proceed.
Procedure
- Identify the change. If not specified, run
openspec list --json and infer only if unambiguous.
- Inspect
openspec status --change <name> --json and existing artifacts.
- If planning artifacts are missing, create ready artifacts using
openspec instructions <artifact> --change <name> --json until apply prerequisites are complete.
- If tasks are incomplete, implement remaining unchecked tasks and update
tasks.md as each task is verified.
- Run relevant project checks and
openspec validate <name>.
- Verify implementation evidence for every requirement and scenario.
- Archive with
openspec archive <name> --yes only when safe or explicitly requested.
- Report exactly what was completed and any blockers left active.
Use this when work was interrupted, partially planned, or partially implemented.
