Creating openspec change
Skill yu-iskw/openspec-skills/skills/creating-openspec-change
Agent Skills to effectively utilize OpenSpec
npx -y skills add yu-iskw/openspec-skills --skill creating-openspec-changeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Creates a new OpenSpec change directory and initial structure. Use when starting a new feature, bugfix, or refactor.
SKILL.md
1.0 KB, 228 tokens by cl100k_base, as published. Nobody here has run it
Creating OpenSpec Change
Purpose
Initializes a new change proposal directory with the standard OpenSpec structure, enabling spec-driven development for a new task.
1. Safety & Verification
- Check Help: Run
npx @fission-ai/openspec@latest new change --help. - Naming: Use a slug-style name (e.g.,
add-dark-mode).
2. Common Workflows
Workflow: Start a New Change
- Run
npx @fission-ai/openspec@latest new change <name>. - This creates a directory under
openspec/changes/<name>/.
3. Error Handling
- If the directory already exists: Choose a different name or manually manage the existing directory.
4. Examples
Example: Create a New Feature Proposal
Command: npx @fission-ai/openspec@latest new change user-auth
Expected Output: A new directory openspec/changes/user-auth/ is created with initial template files.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.