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

261 stars

bypartme-ai

View on GitHub Installation ↓

Best use case

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

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-new" skill to help with this workflow task. Context: 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".

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

$curl -o ~/.claude/skills/openspec-new/SKILL.md --create-dirs "https://raw.githubusercontent.com/partme-ai/full-stack-skills/main/skills/openspec-skills/openspec-new/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/openspec-new/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How openspec-new Compares

Feature / Agent	openspec-new	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?

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

1. **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.

2. **What gets created**
   - `openspec/changes/<name>/` directory.
   - `openspec/changes/<name>/.openspec.yaml` — change metadata (schema, created date).

3. **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.

## 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 list` to see active changes.
- **"Schema not found"**: List available schemas with `openspec schemas`; see **openspec-schema** for custom schemas.

## References

- [OpenSpec Commands: /opsx:new](https://github.com/Fission-AI/OpenSpec/blob/main/docs/commands.md)

Related Skills

openspec-verify

261

from partme-ai/full-stack-skills

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

261

from partme-ai/full-stack-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-sync

261

from partme-ai/full-stack-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-schema

261

from partme-ai/full-stack-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-onboard

261

from partme-ai/full-stack-skills

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-install

261

from partme-ai/full-stack-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-initial

261

from partme-ai/full-stack-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-ff

261

from partme-ai/full-stack-skills

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

261

from partme-ai/full-stack-skills

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.

openspec-continue

261

from partme-ai/full-stack-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-config

261

from partme-ai/full-stack-skills

Configure OpenSpec project settings and global CLI configuration using `openspec/config.yaml` and `openspec config` commands. Use when the user says "configure OpenSpec", "project config", "add project context", or wants to set per-artifact rules.

openspec-bulk-archive

261

from partme-ai/full-stack-skills

Archive multiple completed changes at once with `/opsx:bulk-archive`, handling spec conflicts between changes. Use when the user says "archive all changes", "bulk archive", "/opsx:bulk-archive", or has multiple completed changes.