
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".
- Installs
- 103
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-update- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads openspec-update automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
-
Upgrade the CLI first (if not already done)
npm install -g @fission-ai/openspec@latest(or pnpm/yarn/bun equivalent).
-
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.
-
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.
- Check that
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
FAQ
What does the openspec-update 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".
How do I install openspec-update?
Run npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-update in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/openspec-update/ (personal) or .claude/skills/openspec-update/ (project).
Which AI agents can use openspec-update?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is openspec-update safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains openspec-update?
It is published by full-stack-skills in full-stack-skills/openspec-skills. It has 103 recorded installs.
More from full-stack-skills/openspec-skills
openspec-initial
full-stack-skills/openspec-skills
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-install
full-stack-skills/openspec-skills
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-schema
full-stack-skills/openspec-skills
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-continue
full-stack-skills/openspec-skills
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-sync
full-stack-skills/openspec-skills
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-explore
full-stack-skills/openspec-skills
Open the skill to read its SKILL.md instructions.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.