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".
- 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-new- 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-new 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 New Skill
Use /opsx:new to start a new change. This creates the change folder structure under openspec/changes/<name>/ with metadata (.openspec.yaml) and prepares the first artifact for creation.
When to Use
- Starting work on a new feature, bug fix, or refactor.
- The user says "start a change", "new feature", "new OpenSpec change".
- After exploring ideas with openspec-explore and deciding what to build.
Prerequisites
- OpenSpec initialized in the project (see openspec-initial).
Workflow
-
Start the change
/opsx:new <change-name>— e.g./opsx:new add-dark-mode./opsx:new <change-name> --schema <schema>— use a specific workflow schema (default:spec-driven).- If no name is provided, the agent will prompt for one.
-
What gets created
openspec/changes/<name>/directory.openspec/changes/<name>/.openspec.yaml— change metadata (schema, created date).
-
Next action
- The agent shows the first artifact ready for creation (typically
proposal). - Use openspec-continue to create one artifact at a time, or openspec-ff to create all planning artifacts at once.
- The agent shows the first artifact ready for creation (typically
Naming Conventions
- Use descriptive names:
add-dark-mode,fix-login-bug,refactor-auth. - Avoid generic names:
update,changes,wip. - Use kebab-case.
Outputs
openspec/changes/<name>/directory with.openspec.yaml.
Next Steps
- Use openspec-continue to create the next artifact incrementally.
- Or openspec-ff to fast-forward through all planning artifacts at once.
Troubleshooting
- "Change not found": Check the change name matches; run
openspec listto see active changes. - "Schema not found": List available schemas with
openspec schemas; see openspec-schema for custom schemas.
References
FAQ
What does the openspec-new skill do?
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".
How do I install openspec-new?
Run npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-new 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-new/ (personal) or .claude/skills/openspec-new/ (project).
Which AI agents can use openspec-new?
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-new 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-new?
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-apply
full-stack-skills/openspec-skills
Implement tasks from the change using /opsx:apply, working through the task list and checking off items. Use when the user says "implement", "apply the change", "/opsx:apply", or "start coding from tasks".
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-update
full-stack-skills/openspec-skills
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-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-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-archive
full-stack-skills/openspec-skills
Archive a completed change with /opsx:archive, merging delta specs into main specs and preserving the change for history. Use when the user says "archive the change", "finish up", "/opsx:archive", or "mark this change as done".
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.