openspec-expanded-path

name	openspec-expanded-path
description	Use when working with OpenSpec in Hermes: run the expanded OpenSpec scaffold, fast-forward, apply, verify, and optional archive workflow end to end.
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-expanded-path

This is the single-skill version of OpenSpec's expanded path. Use it when the user wants explicit scaffold semantics but does not want to manually invoke each OpenSpec step.

Flow: new -> ff -> apply -> verify -> archive when safe or requested

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

1. Determine the change name and optional schema.
2. Initialize OpenSpec if needed.
3. Scaffold: openspec new change <name> --json with --schema <schema> if requested.
4. Fast-forward planning:
   • Loop on openspec status --change <name> --json.
   • Generate every ready planning artifact using openspec instructions <artifact> --change <name> --json.
   • Respect custom schemas and dependency order. Do not assume only proposal/specs/design/tasks if the schema differs.
5. Validate: openspec validate <name>.
6. Apply:
   • openspec instructions apply --change <name> --json.
   • Implement task checkboxes in order and update tasks.md after each verified task.
7. Verify:
   • Run project checks.
   • Validate OpenSpec artifacts.
   • Compare implementation against requirements, scenarios, and design.
8. Archive:
   • Archive with openspec archive <name> --yes if fully verified or explicitly requested.
   • Stop and report blockers if validation/tests fail or critical implementation gaps remain.

Use this when users prefer the expanded workflow model but want Hermes to drive all steps in one run.