Official agent skill

Openspec Ff Change

by SAP in SAP/e-mobility-charging-stations-simulator

Fast-forward through OpenSpec artifact creation. An agent skill from SAP/e-mobility-charging-stations-simulator.

OfficialMITAuto-check passed

Install Openspec Ff Change

skills CLI
$ npx skills add SAP/e-mobility-charging-stations-simulator --skill openspec-ff-change -a claude-code

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

GitHub CLI
$ gh skill install SAP/e-mobility-charging-stations-simulator openspec-ff-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/SAP/e-mobility-charging-stations-simulator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/openspec-ff-change .claude/skills/openspec-ff-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-ff-change
GitHub stars
227
Used in
26 other repos
Token cost
~1.1k tokens
SKILL.md length
517 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Fast-forward through OpenSpec artifact creation. An agent skill from SAP/e-mobility-charging-stations-simulator.

  • Works in 5 steps: If no clear input provided, ask what… → Create the change directory → Get the artifact build order → …
  • The user wants to quickly create all artifacts needed for implementation without stepping through each one individually
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Openspec Ff Change is an agent skill from SAP/e-mobility-charging-stations-simulator, published by the product's own GitHub organization. Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

Its SKILL.md is about 1.1k 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: OCPP-J charging stations simulator. The licence is MIT.

When your agent uses it

  • The user wants to quickly create all artifacts needed for implementation without stepping through each one individually

Example prompts

  • “/openspec-ff-change”

Requirements

  • Compatibility (from SKILL.md): Requires openspec CLI.

Workflow steps

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

  1. If no clear input provided, ask what they want to build
  2. Create the change directory
  3. Get the artifact build order
  4. Create artifacts in sequence until apply-ready
  5. Show final status

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    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 Ff Change loads about 1.1k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 517 words of instructions outside code blocks.

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

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 SAP/e-mobility-charging-stations-simulator at commit 1968d3a, republished under its MIT licence (© SAP). 517 words, ~1,096 tokens.

Download SKILL.mdSave it as .claude/skills/openspec-ff-change/SKILL.md (or your agent's skills folder).
name
openspec-ff-change
description
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
compatibility
Requires openspec CLI.
license
MIT
metadata.author
openspec
metadata.version
1.0
metadata.generatedBy
1.3.1

Fast-forward through artifact creation - generate everything needed to start implementation in one go.

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

    Use the AskUserQuestion tool (open-ended, no preset options) to ask:

    "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. Create the change directory

    bash
    openspec new change "<name>"

    This creates a scaffolded change at openspec/changes/<name>/.

  3. Get the artifact build order

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

    Parse the JSON to get:

    • applyRequires: array of artifact IDs needed before implementation (e.g., ["tasks"])
    • artifacts: list of all artifacts with their status and dependencies
  4. Create artifacts in sequence until apply-ready

    Use the TodoWrite tool to track progress through the artifacts.

    Loop through artifacts in dependency order (artifacts with no pending dependencies first):

    a. For each artifact that is ready (dependencies satisfied):

    • Get instructions:
      bash
      openspec instructions <artifact-id> --change "<name>" --json
    • The instructions JSON includes:
      • context: Project background (constraints for you - do NOT include in output)
      • rules: Artifact-specific rules (constraints for you - do NOT include in output)
      • template: The structure to use for your output file
      • instruction: Schema-specific guidance for this artifact type
      • outputPath: Where to write the artifact
      • dependencies: Completed artifacts to read for context
    • Read any completed dependency files for context
    • Create the artifact file using template as the structure
    • Apply context and rules as constraints - but do NOT copy them into the file
    • Show brief progress: "✓ Created <artifact-id>"

    b. Continue until all applyRequires artifacts are complete

    • After creating each artifact, re-run openspec status --change "<name>" --json
    • Check if every artifact ID in applyRequires has status: "done" in the artifacts array
    • Stop when all applyRequires artifacts are done

    c. If an artifact requires user input (unclear context):

    • Use AskUserQuestion tool to clarify
    • Then continue with creation
  5. Show final status

    bash
    openspec status --change "<name>"
Show full SKILL.md (181 more words)Show less

Output

After completing all artifacts, summarize:

  • Change name and location
  • List of artifacts created with brief descriptions
  • What's ready: "All artifacts created! Ready for implementation."
  • Prompt: "Run /opsx-apply or ask me to implement to start working on the tasks."

Artifact Creation Guidelines

  • Follow the instruction field from openspec instructions for each artifact type
  • The schema defines what each artifact should contain - follow it
  • Read dependency artifacts for context before creating new ones
  • Use template as the structure for your output file - fill in its sections
  • IMPORTANT: context and rules are constraints for YOU, not content for the file
    • Do NOT copy <context>, <rules>, <project_context> blocks into the artifact
    • These guide what you write, but should never appear in the output

Guardrails

  • Create ALL artifacts needed for implementation (as defined by schema's apply.requires)
  • Always read dependency artifacts before creating a new one
  • If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
  • If a change with that name already exists, suggest continuing that change instead
  • Verify each artifact file exists after writing before proceeding to next

© SAP, 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 .opencode/skills/openspec-ff-change of SAP/e-mobility-charging-stations-simulator.

Open the folder on GitHubat commit 1968d3a

Used in 27 other repositories

We found 46 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 26 other GitHub owners. This page covers the copy in SAP/e-mobility-charging-stations-simulator, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Openspec Ff 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 Ff Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openspec Ff Change this skillSAP/e-mobility-charging-stations-simulator22726 repos~1.1kAutomated safety check: PassMIT
Artifacts Buildernexu-io/open-design100k—~347Automated safety check: PassApache-2.0
Web Artifacts Builderanthropics/skills180k41 repos~769Automated safety check: PassApache-2.0
Openspec Verify ChangeFission-AI/OpenSpec71k2 repos~4.6kAutomated safety check: PassMIT
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

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 41 repos~769 tokens
    Frontend & DesignAuto-check passed
  • Openspec Verify Change

    Fission-AI/OpenSpec

    Verify implementation matches OpenSpec change artifacts. An agent skill from Fission-AI/OpenSpec.

    71k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-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
  • Best practices for Remotion - Video creation in React. An agent skill from affaan-m/ECC.

    276k GitHub starsUsed in 2 repos~910 tokens
    Media & CreativeAuto-check passed

More from SAP/e-mobility-charging-stations-simulator

  • Openspec Bulk Archive Change

    SAP/e-mobility-charging-stations-simulator

    Official

    Archive multiple completed changes at once. An agent skill from SAP/e-mobility-charging-stations-simulator.

    227 GitHub starsUsed in 25 repos~1.9k tokens
    Auto-check passed
  • Openspec Onboard

    SAP/e-mobility-charging-stations-simulator

    Official

    Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

    227 GitHub starsUsed in 25 repos~3.5k tokens
    Auto-check passed
  • Qmd

    SAP/e-mobility-charging-stations-simulator

    Official

    Search local markdown knowledge bases, notes, docs, and wikis with QMD.

    227 GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check passed
  • Evse Simulator

    SAP/e-mobility-charging-stations-simulator

    Official

    Control and monitor an OCPP charging station simulator via CLI.

    227 GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Openspec Ff Change

What does Openspec Ff Change do?

Fast-forward through OpenSpec artifact creation. An agent skill from SAP/e-mobility-charging-stations-simulator. Openspec Ff Change is an agent skill from SAP/e-mobility-charging-stations-simulator, published by the product's own GitHub organization. Fast-forward through OpenSpec artifact creation.

When should I use Openspec Ff Change?

Openspec Ff Change fits situations like: the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

How do I install Openspec Ff Change in Claude Code?

Run `npx skills add SAP/e-mobility-charging-stations-simulator --skill openspec-ff-change -a claude-code`. Or copy the skill folder (.opencode/skills/openspec-ff-change in SAP/e-mobility-charging-stations-simulator) into .claude/skills/openspec-ff-change in your project. Claude Code loads it when a task matches its description.

How do I install Openspec Ff Change in Codex?

Run `npx skills add SAP/e-mobility-charging-stations-simulator --skill openspec-ff-change -a codex`. Or copy the skill folder (.opencode/skills/openspec-ff-change in SAP/e-mobility-charging-stations-simulator) into .agents/skills/openspec-ff-change in your project. Codex loads it when a task matches its description.

Can I use Openspec Ff 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 SAP/e-mobility-charging-stations-simulator --skill openspec-ff-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-ff-change, .gemini/skills/openspec-ff-change, .github/skills/openspec-ff-change and .opencode/skills/openspec-ff-change in your project.

What does Openspec Ff Change need to run?

SKILL.md names no scripts, command-line tools or credentials: Openspec Ff Change is instructions for the agent only. Compatibility (from SKILL.md): Requires openspec CLI..

Does Openspec Ff 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 Ff 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 Ff Change use?

Openspec Ff 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 Ff Change use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 Ff Change?

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

Who maintains Openspec Ff Change?

SAP (a GitHub organization, an official publisher) maintains it in SAP/e-mobility-charging-stations-simulator, which has 227 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.

Source: SAP/e-mobility-charging-stations-simulator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.