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".
Best use case
openspec-install 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. 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".
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".
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-install" skill to help with this workflow task. Context: 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".
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-install/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How openspec-install Compares
| Feature / Agent | openspec-install | 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?
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".
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 Install Skill
Install the [OpenSpec CLI](https://github.com/Fission-AI/OpenSpec) so that `openspec` is available globally. This skill covers only **installing the CLI**; it does not run `openspec init`. For project initialization after install, use **openspec-initial**.
## When to Use
- First-time OpenSpec setup ("install OpenSpec", "get started with OpenSpec").
- User reports "openspec: command not found".
- Upgrading to the latest version.
- CI or scripts that need the CLI pre-installed.
## Prerequisites
- **Node.js 20.19.0 or higher** — Check with `node --version`. If not installed, guide the user to install Node.js first (e.g. via nvm, fnm, or official installer).
## Workflow
1. **Check if already installed**
- Run `openspec --version`. If it succeeds, the CLI is already installed; suggest **openspec-initial** for project setup or upgrading via `npm install -g @fission-ai/openspec@latest`.
2. **Choose package manager and install**
- **npm** (most common): `npm install -g @fission-ai/openspec@latest`
- **pnpm**: `pnpm add -g @fission-ai/openspec@latest`
- **yarn**: `yarn global add @fission-ai/openspec@latest`
- **bun**: `bun add -g @fission-ai/openspec@latest`
- **nix** (one-time, no install): `nix run github:Fission-AI/OpenSpec -- init`
- **nix** (persistent): `nix profile install github:Fission-AI/OpenSpec`
3. **Verify installation**
- Run `openspec --version` to confirm.
4. **Upgrade existing installation**
- Same command as install — e.g. `npm install -g @fission-ai/openspec@latest`.
## Outputs
- `openspec` command available globally in PATH.
## Next Steps
- Use **openspec-initial** to run `openspec init` in a project.
- Or use **openspec-onboard** for a guided tutorial.
## Different Environments
| Environment | Command |
|-------------|---------|
| **npm** | `npm install -g @fission-ai/openspec@latest` |
| **pnpm** | `pnpm add -g @fission-ai/openspec@latest` |
| **yarn** | `yarn global add @fission-ai/openspec@latest` |
| **bun** | `bun add -g @fission-ai/openspec@latest` |
| **nix (one-time)** | `nix run github:Fission-AI/OpenSpec -- init` |
| **nix (persistent)** | `nix profile install github:Fission-AI/OpenSpec` |
| **CI** | `npm install -g @fission-ai/openspec@latest` in a cacheable step |
## Troubleshooting
- **Node.js version too old**: OpenSpec requires Node.js 20.19.0+. Upgrade Node.js first.
- **Permission errors (npm)**: Use `npm install -g` without sudo if using nvm/fnm; otherwise consider using nvm.
- **Command not found after install**: Ensure the global bin directory is in PATH (check `npm bin -g`).
- **nix not available**: Install nix or use npm/pnpm/yarn/bun instead.
## References
- [OpenSpec Installation docs](https://github.com/Fission-AI/OpenSpec/blob/main/docs/installation.md)
- [OpenSpec GitHub](https://github.com/Fission-AI/OpenSpec)Related Skills
skill-installer
Discovers, installs, and manages AI skills from the PartMe marketplace. Acts as the local package manager for Knowledge-as-a-Service (KaaS) and Tool-as-a-Service (TaaS) skills. Use when the user wants to search for available skills, install a new skill into their environment, or list currently installed skills.
tui-install
Generate and render a pixel-precise ASCII TUI Install Guide component with complete output blocks (TUI_RENDER, COMPONENT_SPEC, PENCIL_SPEC, PENCIL_BATCH_DESIGN) for Pencil MCP drawing workflows. Use when the user asks to create an install in a terminal UI, text-based interface, or Pencil MCP project.
speckit-install
Install the Specify CLI on the host machine (uv tool install or uvx one-time); supports multiple OS, persistent or one-time install, and corporate or restricted-network environments. Use when the user says "install Spec Kit", "install Specify CLI", or "specify command not found".
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-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".
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-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.