AI Agent Skill HUB
multiAI Summary Pending

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

223 stars
bypartme-ai
View on GitHubInstallation ↓

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

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

How openspec-new Compares

Feature / Agentopenspec-newStandard Approach
Platform SupportmultiLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this 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".

Which AI agents support this skill?

This skill is compatible with multi.

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)