openspec-update
Run `openspec update` to regenerate AI tool instruction files after upgrading the OpenSpec CLI. Use when the user says "update OpenSpec", "openspec update", or "refresh OpenSpec skills/commands".
Best use case
openspec-update is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Run `openspec update` to regenerate AI tool instruction files after upgrading the OpenSpec CLI. Use when the user says "update OpenSpec", "openspec update", or "refresh OpenSpec skills/commands".
Run `openspec update` to regenerate AI tool instruction files after upgrading the OpenSpec CLI. Use when the user says "update OpenSpec", "openspec update", or "refresh OpenSpec skills/commands".
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "openspec-update" skill to help with this workflow task. Context: Run `openspec update` to regenerate AI tool instruction files after upgrading the OpenSpec CLI. Use when the user says "update OpenSpec", "openspec update", or "refresh OpenSpec skills/commands".
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/openspec-update/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How openspec-update Compares
| Feature / Agent | openspec-update | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run `openspec update` to regenerate AI tool instruction files after upgrading the OpenSpec CLI. Use when the user says "update OpenSpec", "openspec update", or "refresh OpenSpec skills/commands".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# OpenSpec Update Skill Run **openspec update** to regenerate AI tool configuration files (skills, commands, rules) after upgrading the OpenSpec CLI package. This ensures your project uses the latest slash commands and skill instructions. ## When to Use - After upgrading the OpenSpec CLI (`npm install -g @fission-ai/openspec@latest`). - When slash commands or skills seem outdated or missing. - After changing tool selections and wanting to refresh configs. ## Prerequisites - **OpenSpec CLI** installed (see **openspec-install**). - **Project initialized** with `openspec init` (see **openspec-initial**). ## Workflow 1. **Upgrade the CLI first** (if not already done) - `npm install -g @fission-ai/openspec@latest` (or pnpm/yarn/bun equivalent). 2. **Run update** - `openspec update` — regenerates AI tool config files. - `openspec update --force` — force update even when files are up to date. - `openspec update ./my-project` — target a specific directory. 3. **Verify** - Check that `.claude/skills/`, `.cursor/rules/`, or other tool directories have been refreshed. - Restart your AI tool to pick up new skills if needed. ## Outputs - Regenerated tool-specific config files (skills, commands, rules) matching the new CLI version. ## Next Steps - Continue your workflow with **openspec-new**, **openspec-explore**, etc. ## Troubleshooting - **"openspec: command not found"**: Use **openspec-install** first. - **"Project not initialized"**: Run **openspec-initial** (`openspec init`) first. - **Skills not appearing after update**: Restart your AI tool (Claude Code, Cursor, etc.) to reload skills. ## References - [OpenSpec CLI: update](https://github.com/Fission-AI/OpenSpec/blob/main/docs/cli.md)
Related Skills
tauri-app-updater
Configure OTA (over-the-air) app updates using the Tauri v2 updater plugin with signing keys and update server setup. Use when implementing auto-update checks, generating signing key pairs, or configuring update server endpoints and metadata.
openspec-verify
Validate that implementation matches change artifacts using `/opsx:verify`, checking completeness, correctness, and coherence. Use when the user says "verify implementation", "check my work", "/opsx:verify", or wants quality validation before archiving.
openspec-sync
Sync delta specs from a change into main specs using `/opsx:sync`, without archiving the change. Use when the user says "sync specs", "merge specs to main", "/opsx:sync", or needs to update main specs mid-change.
openspec-schema
Create and manage custom workflow schemas using `openspec schema init/fork/validate/which`. Use when the user says "create a custom workflow", "custom schema", "fork a schema", or wants to define their own artifact types and dependencies.
openspec-onboard
Guided onboarding through the complete OpenSpec workflow using `/opsx:onboard`, walking the user through a real change in their codebase. Use when the user says "onboard me", "tutorial", "/opsx:onboard", "how does OpenSpec work", or is new to OpenSpec.
openspec-new
Start a new OpenSpec change with `/opsx:new`, creating a change folder with metadata and scaffolding. Use when the user says "start a new change", "new feature", "/opsx:new", or "create an OpenSpec change".
openspec-install
Install the OpenSpec CLI globally via npm, pnpm, yarn, bun, or nix. Use when the user says "install OpenSpec", "set up OpenSpec", or "openspec command not found".
openspec-initial
Run `openspec init` to initialize OpenSpec in a project directory, creating the openspec/ folder structure and configuring AI tool integrations. Use when the user says "initialize OpenSpec", "openspec init", or "set up OpenSpec in this project".
openspec-ff
Fast-forward through artifact creation with `/opsx:ff`, generating all planning artifacts (proposal, specs, design, tasks) at once. Use when the user says "fast forward", "create all artifacts", "/opsx:ff", or has a clear picture of what to build.
openspec-explore
Think through ideas, investigate problems, and clarify requirements before committing to a change using `/opsx:explore`. Use when the user says "explore an idea", "think through this", "investigate options", or wants to brainstorm before creating a formal change.
openspec-continue
Create the next artifact in the dependency chain with `/opsx:continue`, building up a change incrementally. Use when the user says "continue the change", "create next artifact", "/opsx:continue", or wants step-by-step artifact creation.
openspec-config
Configure OpenSpec project settings and global CLI configuration using `openspec/config.yaml` and `openspec config` commands. Use when the user says "configure OpenSpec", "project config", "add project context", or wants to set per-artifact rules.