How do I install the Openspec Initial skill?

Run npx skillmds@latest add diegosouzapw/openspec-initial in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openspec Initial safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openspec Initial?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openspec Initial free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openspec Initial?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openspec Initial by diegosouzapw — Agent Skill

Name: Openspec Initial
Rating: 4.666666666666667 (3 reviews)
Author: diegosouzapw

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".

diegosouzapw Updated Sep 8, 2026 54 repo stars

File contents

OpenSpec Initial Skill

Run openspec init to initialize OpenSpec in a project: creates the openspec/ directory (specs, changes, config) and configures AI tool integrations (skills and slash commands). This skill assumes the OpenSpec CLI is already installed; if not, direct the user to openspec-install first.

When to Use

First time enabling OpenSpec in a project ("initialize OpenSpec", "set up OpenSpec here").
Adding AI tool integrations (Claude, Cursor, Windsurf, etc.) to an existing project.
Re-initializing after changing tool selections.

Prerequisites

OpenSpec CLI installed (see openspec-install). If openspec is not in PATH, guide the user to run openspec-install before proceeding.

Workflow

Verify CLI
- If the user reports "openspec command not found", direct them to openspec-install first.
Choose parameters
- path (optional): Target directory; defaults to current directory.
- --tools (optional): Configure AI tools non-interactively. Values: all, none, or comma-separated list (e.g. claude,cursor).
- --force: Auto-cleanup legacy files without prompting.
Run the command
- Interactive: openspec init
- Non-interactive with specific tools: openspec init --tools claude,cursor
- All tools: openspec init --tools all
- Specific directory: openspec init ./my-project
Optionally create project config
- During init, the user may be prompted to create openspec/config.yaml with project context, schema defaults, and per-artifact rules. This is optional but recommended. See openspec-config for details.
Confirm outputs
- After success: openspec/ directory with specs/, changes/, and optionally config.yaml. Tool-specific directories (.claude/skills/, .cursor/rules/, etc.) are created based on selected tools.

Supported Tools

amazon-q, antigravity, auggie, claude, cline, codebuddy, codex, continue, costrict, crush, cursor, factory, gemini, github-copilot, iflow, kilocode, opencode, qoder, qwen, roocode, trae, windsurf

Outputs

openspec/:
- specs/ — Specifications (source of truth)
- changes/ — Proposed changes
- config.yaml — Project configuration (optional)
Tool configs: .claude/skills/, .cursor/rules/, .windsurf/skills/, etc. based on selected tools.

Next Steps

Use openspec-update after upgrading the CLI to regenerate tool configs.
Use openspec-onboard for a guided walkthrough of the complete workflow.
Or start working: openspec-explore to think through ideas, openspec-new to start a change.

Different Environments

Scenario	Command
Interactive	`openspec init`
Claude + Cursor	`openspec init --tools claude,cursor`
All tools	`openspec init --tools all`
Specific directory	`openspec init ./my-project`
CI / non-interactive	`openspec init --tools claude --force`
Skip tool config	`openspec init --tools none`

Troubleshooting

"openspec: command not found": Use openspec-install first.
Legacy files detected: Use --force to auto-cleanup, or follow the interactive prompts.
Tool not in list: Check the supported tools list for the correct ID.

References

---name: openspec-initialdescription: 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 Initial SkillRun **openspec init** to initialize OpenSpec in a project: creates the `openspec/` directory (specs, changes, config) and configures AI tool integrations (skills and slash commands). This skill assumes the OpenSpec CLI is already installed; if not, direct the user to **openspec-install** first.## When to Use- First time enabling OpenSpec in a project ("initialize OpenSpec", "set up OpenSpec here").- Adding AI tool integrations (Claude, Cursor, Windsurf, etc.) to an existing project.- Re-initializing after changing tool selections.## Prerequisites- **OpenSpec CLI** installed (see **openspec-install**). If `openspec` is not in PATH, guide the user to run **openspec-install** before proceeding.## Workflow1. **Verify CLI** - If the user reports "openspec command not found", direct them to **openspec-install** first.2. **Choose parameters** - **path** (optional): Target directory; defaults to current directory. - **--tools** (optional): Configure AI tools non-interactively. Values: `all`, `none`, or comma-separated list (e.g. `claude,cursor`). - **--force**: Auto-cleanup legacy files without prompting.3. **Run the command** - Interactive: `openspec init` - Non-interactive with specific tools: `openspec init --tools claude,cursor` - All tools: `openspec init --tools all` - Specific directory: `openspec init ./my-project`4. **Optionally create project config** - During init, the user may be prompted to create `openspec/config.yaml` with project context, schema defaults, and per-artifact rules. This is optional but recommended. See **openspec-config** for details.5. **Confirm outputs** - After success: `openspec/` directory with `specs/`, `changes/`, and optionally `config.yaml`. Tool-specific directories (`.claude/skills/`, `.cursor/rules/`, etc.) are created based on selected tools.## Supported Tools`amazon-q`, `antigravity`, `auggie`, `claude`, `cline`, `codebuddy`, `codex`, `continue`, `costrict`, `crush`, `cursor`, `factory`, `gemini`, `github-copilot`, `iflow`, `kilocode`, `opencode`, `qoder`, `qwen`, `roocode`, `trae`, `windsurf`## Outputs- **openspec/**: - `specs/` — Specifications (source of truth) - `changes/` — Proposed changes - `config.yaml` — Project configuration (optional)- **Tool configs**: `.claude/skills/`, `.cursor/rules/`, `.windsurf/skills/`, etc. based on selected tools.## Next Steps- Use **openspec-update** after upgrading the CLI to regenerate tool configs.- Use **openspec-onboard** for a guided walkthrough of the complete workflow.- Or start working: **openspec-explore** to think through ideas, **openspec-new** to start a change.## Different Environments| Scenario | Command ||----------|---------|| **Interactive** | `openspec init` || **Claude + Cursor** | `openspec init --tools claude,cursor` || **All tools** | `openspec init --tools all` || **Specific directory** | `openspec init ./my-project` || **CI / non-interactive** | `openspec init --tools claude --force` || **Skip tool config** | `openspec init --tools none` |## Troubleshooting- **"openspec: command not found"**: Use **openspec-install** first.- **Legacy files detected**: Use `--force` to auto-cleanup, or follow the interactive prompts.- **Tool not in list**: Check the [supported tools list](https://github.com/Fission-AI/OpenSpec/blob/main/docs/supported-tools.md) for the correct ID.## References- [OpenSpec CLI: init](https://github.com/Fission-AI/OpenSpec/blob/main/docs/cli.md)- [OpenSpec Supported Tools](https://github.com/Fission-AI/OpenSpec/blob/main/docs/supported-tools.md)

Frequently asked questions