Stats
Actions
Tags
From openspec
Check if the OpenSpec plugin methodology and schema templates have been updated in the upstream Fission-AI/OpenSpec repository. Use when the user wants to sync with upstream, says "check for updates", "sync openspec", "update methodology", or wants to ensure they are using the latest OpenSpec workflow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/openspec:check-updatesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are checking whether the upstream [Fission-AI/OpenSpec](https://github.com/Fission-AI/OpenSpec) repository has been updated since this plugin's skills were last synchronized. This helps you stay current with the latest OpenSpec OPSX methodology.
You are checking whether the upstream Fission-AI/OpenSpec repository has been updated since this plugin's skills were last synchronized. This helps you stay current with the latest OpenSpec OPSX methodology.
This plugin's skills were derived from the OpenSpec repository (commit afdca0d5dab1aa109cfd8848b2512333ccad60c3). The upstream evolves — workflows improve, new schemas are added, and the methodology is refined.
The sync metadata is stored in openspec/config.yaml (the standard OpenSpec config location) with an additional _plugin_sync section:
# openspec/config.yaml
schema: spec-driven
context: |
[Your project context]
_plugin_sync:
source: "github.com/Fission-AI/OpenSpec"
source_sha: "[last known upstream commit SHA]"
last_checked: "[date]"
plugin_version: "1.0.0"
Read openspec/config.yaml if it exists and look for _plugin_sync:
_plugin_sync:
source: "github.com/Fission-AI/OpenSpec"
source_sha: "afdca0d5dab1aa109cfd8848b2512333ccad60c3"
last_checked: "[date]"
plugin_version: "1.0.0"
If openspec/config.yaml doesn't exist, create it with default content:
schema: spec-driven
_plugin_sync:
source: "github.com/Fission-AI/OpenSpec"
source_sha: "afdca0d5dab1aa109cfd8848b2512333ccad60c3"
last_checked: "[TODAY]"
plugin_version: "1.0.0"
Check the upstream repository for recent changes using one of these methods (in preference order):
Method 1: Via GitHub API
https://api.github.com/repos/Fission-AI/OpenSpec/commits/mainhttps://api.github.com/repos/Fission-AI/OpenSpec/releases/latestMethod 2: Via npm registry (OpenSpec is published as @fission-ai/openspec)
https://registry.npmjs.org/@fission-ai/openspec/latestMethod 3: Offline Report that internet access is needed and provide manual check instructions.
OpenSpec Update Status
======================
Plugin version: [current plugin version]
Last checked: [date from config, or "never"]
Known upstream SHA: [SHA from config]
Current upstream SHA: [SHA from GitHub API]
Latest npm release: [version from npm registry]
Determine status:
If updates are available, report what changed since the last known SHA:
https://api.github.com/repos/Fission-AI/OpenSpec/commits?since=[last_checked]&per_page=20https://raw.githubusercontent.com/Fission-AI/OpenSpec/main/CHANGELOG.mdCategorize changes:
schemas/spec-driven/ templatesUpdates Available in Fission-AI/OpenSpec
=========================================
Time since last check: [N days/weeks]
npm version: [current] → [latest]
Commits since sync: [N]
Notable Changes:
📝 schemas/spec-driven/schema.yaml — updated workflow instructions
🆕 New command: /opsx:onboard added
🔧 /opsx:apply — improved task tracking
For full changelog: https://github.com/Fission-AI/OpenSpec/blob/main/CHANGELOG.md
npm install: npm install -g @fission-ai/openspec@latest
If schema templates changed (in schemas/spec-driven/templates/):
Action: Schema template updates available
Your local OpenSpec schema templates may be outdated.
To update the schema templates for your project:
Option 1: Reinstall OpenSpec CLI and re-initialize
npm install -g @fission-ai/openspec@latest
openspec update (from your project directory)
Option 2: Manually update schema templates
The templates are in openspec/schemas/spec-driven/templates/ (if customized)
Check the upstream templates at:
https://github.com/Fission-AI/OpenSpec/tree/main/schemas/spec-driven/templates
If workflow commands changed (skills SKILL.md files):
Action: Plugin skill updates available
The OpenSpec plugin skills may have outdated methodology.
To get the latest skills, contact your plugin maintainer
or check the upstream workflow documentation at:
https://github.com/Fission-AI/OpenSpec/blob/main/docs/opsx.md
Plugin source: plugins/openspec/skills/
If only minor changes (bug fixes, minor improvements):
Minor updates available. The changes are backwards compatible.
You can continue using the current plugin safely.
To get the latest methodology updates, update the plugin.
If no changes:
✅ Your OpenSpec plugin is up to date!
Last checked: [today's date]
npm version: [version]
Upstream SHA: [SHA]
Update openspec/config.yaml with today's check date (preserve all other content):
_plugin_sync:
source: "github.com/Fission-AI/OpenSpec"
source_sha: "[latest SHA, or unchanged if check failed]"
last_checked: "[TODAY'S DATE]"
plugin_version: "1.0.0"
npm outdated -g @fission-ai/openspec shows if the npm package is out of datenpx claudepluginhub chenxizhang/agent-skills-and-plugins --plugin openspecProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.