DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to switch to the expanded workflow and archive many changes at once with Open Spec

Enable the full set of Open Spec commands and clear finished changes in one pass.

Who it is forA developer or team lead who has finished several changes in a project and wants to close them out together and use finer-grained commands.

The problemFinished changes pile up in openspec/changes/ and each needs separate archiving when they are done one by one.

The outcomeThe expanded command set is active in the project, and finished changes are archived in one bulk run with specs updated.

What you need first

  • Node.js 20.19.0 or higher, or Homebrew on macOS or Linux
  • A project directory you want to use OpenSpec in
  • An AI coding assistant that OpenSpec supports (30+ tools listed in the docs)

Steps

  1. Run npm install -g @fission-ai/openspec@latest to make sure the CLI is current
  2. Run openspec config profile and select the expanded workflow
  3. Run openspec update inside the project to regenerate agent instructions and activate the new slash commands
  4. In your AI assistant, run /opsx:verify on each finished change, then run /opsx:bulk-archive

Prompt for your agent

In the Fission-AI/OpenSpec project at <project-path>, select the expanded workflow with `openspec config profile`, then run `openspec update`. Expected output: the new commands such as /opsx:verify and /opsx:bulk-archive are listed as active for your assistant. Verify that openspec/changes/ lists the finished changes before running /opsx:bulk-archive.

Caveat. The README says the expanded commands need profile selection and `openspec update`, and it does not describe how bulk archive chooses which changes to archive, so check the list before confirming.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page