New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Openspec New Change

by elastic in elastic/terraform-provider-elasticstack

Start a new OpenSpec change using the experimental artifact workflow.

OfficialMITAuto-check passed

Install Openspec New Change

skills CLI
$ npx skills add elastic/terraform-provider-elasticstack --skill openspec-new-change -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install elastic/terraform-provider-elasticstack openspec-new-change --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/elastic/terraform-provider-elasticstack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/openspec-new-change .claude/skills/openspec-new-change && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
openspec-new-change
GitHub stars
210
Used in
30 other repos
Token cost
~943 tokens
SKILL.md length
476 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Start a new OpenSpec change using the experimental artifact workflow.

  • Works in 6 steps: If no clear input provided, ask what… → Determine the workflow schema → Create the change directory → …
  • The user wants to create a new feature
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Modification with a structured step-by-step approach

What it does

Openspec New Change is an agent skill from elastic/terraform-provider-elasticstack, published by the product's own GitHub organization. Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires openspec CLI.

The repository describes itself as: Terraform provider for Elastic Stack. The licence is MIT.

When your agent uses it

  • The user wants to create a new feature
  • Modification with a structured step-by-step approach

Example prompts

  • “/openspec-new-change”

Requirements

  • Compatibility (from SKILL.md): Requires openspec CLI.
  • Pre-approved tools (allowed-tools): Bash(openspec:*)

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. If no clear input provided, ask what they want to build
  2. Determine the workflow schema
  3. Create the change directory
  4. Show the artifact status
  5. Get instructions for the first artifact
  6. STOP and wait for user direction

What it can do on your machine

Read from SKILL.md and the folder at commit ab9d355. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(openspec:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires openspec CLI.

    From compatibility in the SKILL.md frontmatter.

Context cost

Openspec New Change loads about 943 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 476 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~943

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from elastic/terraform-provider-elasticstack at commit ab9d355, republished under its MIT licence (© elastic). 476 words, ~943 tokens.

Download SKILL.mdSave it as .claude/skills/openspec-new-change/SKILL.md (or your agent's skills folder).
name
openspec-new-change
description
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
allowed-tools
Bash(openspec:*)
compatibility
Requires openspec CLI.
license
MIT
metadata.author
openspec
metadata.version
1.0
metadata.generatedBy
1.12.0

Start a new change using the experimental artifact-driven approach.

Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context, schemas, view). Once selected, treat --store <id> as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run openspec status --change "<name>" --json --store "<id>", not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.

Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.

Steps

  1. If no clear input provided, ask what they want to build

    Ask the user (open-ended, no preset options):

    "What change do you want to work on? Describe what you want to build or fix."

    From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).

    IMPORTANT: Do NOT proceed without understanding what the user wants to build.

  2. Determine the workflow schema

    Use the default schema (omit --schema) unless the user explicitly requests a different workflow.

    Use a different schema only if the user mentions:

    • A specific schema name → use --schema <name>
    • "show workflows" or "what workflows" → run openspec schemas --json and let them choose

    Otherwise: Omit --schema to use the default.

  3. Create the change directory

    bash
    openspec new change "<name>"

    Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change in the planning home resolved by the CLI.

  4. Show the artifact status

    bash
    openspec status --change "<name>" --json

    Use the returned planningHome, changeRoot, artifactPaths, and nextSteps instead of assuming repo-local paths.

  5. Get instructions for the first artifact The first artifact depends on the schema (e.g., proposal for spec-driven). Check the status output to find the first artifact with status "ready".

    bash
    openspec instructions <first-artifact-id> --change "<name>"

    This outputs the template and context for creating the first artifact.

  6. STOP and wait for user direction

Show full SKILL.md (103 more words)Show less

Output

After completing the steps, summarize:

  • Change name and location
  • Schema/workflow being used and its artifact sequence
  • Current status (0/N artifacts complete)
  • The template for the first artifact
  • Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."

Guardrails

  • Do NOT create any artifacts yet - just show the instructions
  • Do NOT advance beyond showing the first artifact template
  • If the name is invalid (not kebab-case), ask for a valid name
  • If a change with that name already exists, suggest continuing that change instead
  • Pass --schema if using a non-default workflow

© elastic, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/openspec-new-change of elastic/terraform-provider-elasticstack.

Open the folder on GitHubat commit ab9d355

Used in at least 31 other repositories

We found 55 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 30 other GitHub owners. This page covers the copy in elastic/terraform-provider-elasticstack, which our catalogue first saw on October 7, 2026.

…and 5 more copies not listed here.

Compare with similar skills

Openspec New Change next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Openspec New Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openspec New Change this skillelastic/terraform-provider-elasticstack21030 repos~943Automated safety check: PassMIT
Artifacts Buildernexu-io/open-design100k—~347Automated safety check: PassApache-2.0
Web Artifacts Builderanthropics/skills180k40 repos~769Automated safety check: PassApache-2.0
Web Artifacts Buildernexu-io/open-design100k—~337Automated safety check: PassApache-2.0
Web Artifacts Buildersickn33/agentic-awesome-skills47k3 repos~824Automated safety check: PassApache-2.0
Artifact Diagrammingasgeirtj/system_prompts_leaks69k—~1kAutomated safety check: PassCC0-1.0

Similar skills

  • Artifacts Builder

    nexu-io/open-design

    Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).

    100k GitHub stars~347 tokensUpdated today
    Frontend & DesignAuto-check passed

  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 40 repos~769 tokens
    Frontend & DesignAuto-check passed

  • Web Artifacts Builder

    nexu-io/open-design

    Build complex claude.ai HTML artifacts with React and Tailwind.

    100k GitHub stars~337 tokensUpdated today
    Frontend & DesignAuto-check passed

  • Web Artifacts Builder

    sickn33/agentic-awesome-skills

    To build powerful frontend claude.ai artifacts, follow these steps:

    47k GitHub starsUsed in 3 repos~824 tokens
    Frontend & DesignAuto-check passed

  • Artifact Diagramming

    asgeirtj/system_prompts_leaks

    Diagramming know-how for Artifacts - when a picture earns its place, how to draw one that shows the real mechanism, and the inline-SVG mechanics that keep it legible in both themes.

    69k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Artifact Capabilities

    asgeirtj/system_prompts_leaks

    Runtime capabilities a published Artifact page can be granted — behavior static HTML cannot provide on its own, such as the page reading live or connected data, remembering what people do on it (a…

    69k GitHub stars~4.3k tokensUpdated today
    Auto-check passed

More from elastic/terraform-provider-elasticstack

All 21 skills in this repo

  • Openspec Explore

    elastic/terraform-provider-elasticstack

    Official

    Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements.

    210 GitHub starsUsed in 85 repos~4.6k tokens
    Auto-check passed

  • Openspec Apply Change

    elastic/terraform-provider-elasticstack

    Official

    Implement tasks from an OpenSpec change. An agent skill from elastic/terraform-provider-elasticstack.

    210 GitHub starsUsed in 92 repos~2.1k tokens
    Auto-check passed

  • Openspec Archive Change

    elastic/terraform-provider-elasticstack

    Official

    Archive a completed change in the experimental workflow. An agent skill from elastic/terraform-provider-elasticstack.

    210 GitHub starsUsed in 85 repos~2.7k tokens
    Auto-check passed

  • PR Monitoring Loop

    elastic/terraform-provider-elasticstack

    Official

    Monitor GitHub pull requests through a subagent-based loop that watches CI checks, review comments, PR comments, review state, merge conflicts, and branch freshness.

    210 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

  • Openspec Plus Proposal

    elastic/terraform-provider-elasticstack

    Official

    MANDATORY skill that activates whenever the OpenSpec proposal phase begins.

    210 GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed

  • Openspec Propose

    elastic/terraform-provider-elasticstack

    Official

    Propose a new change with all artifacts generated in one step.

    210 GitHub starsUsed in 78 repos~3.1k tokens
    Auto-check passed

Questions about Openspec New Change

What does Openspec New Change do?

Start a new OpenSpec change using the experimental artifact workflow. Openspec New Change is an agent skill from elastic/terraform-provider-elasticstack, published by the product's own GitHub organization. Start a new OpenSpec change using the experimental artifact workflow.

When should I use Openspec New Change?

Openspec New Change fits situations like: the user wants to create a new feature; modification with a structured step-by-step approach.

How do I install Openspec New Change in Claude Code?

Run `npx skills add elastic/terraform-provider-elasticstack --skill openspec-new-change -a claude-code`. Or copy the skill folder (.agents/skills/openspec-new-change in elastic/terraform-provider-elasticstack) into .claude/skills/openspec-new-change in your project. Claude Code loads it when a task matches its description.

How do I install Openspec New Change in Codex?

Run `npx skills add elastic/terraform-provider-elasticstack --skill openspec-new-change -a codex`. Or copy the skill folder (.agents/skills/openspec-new-change in elastic/terraform-provider-elasticstack) into .agents/skills/openspec-new-change in your project. Codex loads it when a task matches its description.

Can I use Openspec New Change in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add elastic/terraform-provider-elasticstack --skill openspec-new-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openspec-new-change, .gemini/skills/openspec-new-change, .github/skills/openspec-new-change and .opencode/skills/openspec-new-change in your project.

What does Openspec New Change need to run?

SKILL.md names no scripts, command-line tools or credentials: Openspec New Change is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(openspec:*). Compatibility (from SKILL.md): Requires openspec CLI..

Does Openspec New Change access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Openspec New Change safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Openspec New Change use?

Openspec New Change is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Openspec New Change use?

About 943 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Openspec New Change?

Skills that share tags, products or a category with Openspec New Change: Artifacts Builder (nexu-io/open-design, 100k stars), Web Artifacts Builder (anthropics/skills, 180k stars), Web Artifacts Builder (nexu-io/open-design, 100k stars) and Web Artifacts Builder (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Openspec New Change?

elastic (a GitHub organization, an official publisher) maintains it in elastic/terraform-provider-elasticstack, which has 210 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 10, 2026.

Source: elastic/terraform-provider-elasticstack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.