agentsclimarketplace
Sign in

Openspec expanded path

Skill TheSmuks/openspec-hermes/skills/openspec/openspec-expanded-path

Use when working with OpenSpec in Hermes: run the expanded OpenSpec scaffold, fast-forward, apply, verify, and optional archive workflow end to end.From its SKILL.md

Install
npx -y skills add TheSmuks/openspec-hermes --skill openspec-expanded-path

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, 488 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.