К основному содержанию
скилл CX Codex

openspec-ff-change — скилл для Claude Code: создание артефактов

Скилл openspec-ff-change для Claude Code, который проводит создание артефактов OpenSpec за один проход. Запускается по просьбе быстро подготовить всё для начала реализации или по командам openspec ff и opsx ff.

MIT 4 500 установок ★ 75 426 обновлён 2026-11-16

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add Fission-AI/OpenSpec --skill openspec-ff-change -a claude-code
Открыть на GitHub

Что делает openspec-ff-change

Скилл создаёт OpenSpec change и готовит необходимые артефакты для начала реализации. Он получает порядок сборки из статуса change, читает инструкции для каждого артефакта и учитывает зависимости между ними.

Перед записью проверяется корень проекта через OpenSpec CLI. Если корня нет, скилл не создаёт его сам: при явном запросе OpenSpec он спрашивает, настроить ли проект, выбрать store или продолжить без OpenSpec. Для работы нужен установленный openspec CLI и проект, уже использующий OpenSpec. Если выбран store, его ID передаётся в командах чтения и записи на протяжении всего процесса.

Какие задачи решает

  • подготовить артефакты OpenSpec для реализации одной change
  • создать change по описанию задачи
  • собрать зависимые артефакты в нужном порядке
  • обработать запросы openspec ff и opsx ff

Примеры запросов агенту

  • Подготовь все артефакты OpenSpec для добавления авторизации пользователей.
  • Запусти openspec ff для изменения системы входа.
  • Используй opsx ff, чтобы быстро создать планируемые артефакты для исправления ошибки.

Как установить openspec-ff-change

1Через Skills CLI (Vercel)

npx skills add Fission-AI/OpenSpec --skill openspec-ff-change -a claude-code

2Вручную: положить файлы

~/.claude/skills/openspec-ff-change/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/openspec-ff-change/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы об openspec-ff-change

Как установить openspec-ff-change в Claude Code?

Выполни npx skills add Fission-AI/OpenSpec --skill openspec-ff-change -a claude-code. Файл скилла находится по пути ~/.claude/skills/openspec-ff-change/SKILL.md.

Что делает openspec-ff-change?

Создаёт OpenSpec change и формирует все нужные для начала реализации артефакты, следуя их зависимостям и инструкциям.

Что нужно для работы openspec-ff-change?

Нужны установленный OpenSpec CLI и проект, который уже использует OpenSpec.

Исходный текст

SKILL.md · MIT
---
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. Also use when the user says "openspec ff" or "opsx ff".
allowed-tools: Bash(openspec:*)
license: MIT
compatibility: Requires openspec CLI.
metadata:
  author: openspec
  version: "1.0"
---

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

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

**Project check:** These steps expect a project that already uses OpenSpec. Before the first step that writes anything (`new change`, `archive`, `sync specs`, or authoring an artifact file), confirm the project has a root: run `openspec list --json` (with `--store <id>` when a store is selected, since the store is then the root) and read `root`. A root object means the project is set up. `"root": null` means it is not - there is no `openspec/` directory here, and a write such as `openspec new change` would create one as a side effect. The command also exits non-zero, which is that answer rather than a broken CLI, so read the JSON instead of retrying or working around it.

One `"root": null` is not about setup: when a `status` error message starts with `Declared in` or `Invalid store declaration in` and names this project's `openspec/config.yaml` (or `config.yml`), the project does use OpenSpec through a store it declares, which this machine cannot resolve (the store is not registered, or the `store:` line is malformed). Do not treat it as uninitialized and skip the branches below: stop before writing and show the user that error's `message` and `fix`.

Otherwise, with no root, what happens next depends on how this workflow was reached:

- **Auto-selected**: you chose this workflow yourself, without the user naming OpenSpec, naming this skill, or invoking this skill by name. Stop using OpenSpec and answer the request normally, as you would with no OpenSpec installed. Do not ask them to set anything up and do not mention OpenSpec setup.
- **Explicit OpenSpec request**: the user named OpenSpec, named this skill, or invoked this skill by name. Stop before writing and ask how to proceed: set this project up (`openspec init`), target a store they already have (`--store <id>`), or continue without OpenSpec for this request. Wait for their answer.

In both branches, never create the root as a side effect: do not run `openspec init` until the user asks for it, do not hand-create `openspec/` files, and do not let a command create it.

**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. **Create the change directory**
   ```bash
   openspec new change "<name>"
   ```
   This creates a scaffolded change in the planning home resolved by the CLI.

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, each with its `status` and its `requires` edges (the artifact IDs it directly depends on)
   - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.

4. **Create every artifact in the required set**

   Use a todo list 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
        - `skipped`/`warning`: present when the change declares skip_specs and this artifact must NOT be created - stop and pick another artifact
        - `resolvedOutputPath`: Resolved path or pattern to write the artifact
        - `dependencies`: Completed artifacts to read for context
      - Read any completed dependency files for context - always re-read them from disk, even if you saw them earlier in the conversation (the user may have edited them)
      - **Inspect the relevant project before drafting**: Read `context` and `rules` first, then inspect relevant implementation, nearby tests, configuration, and documentation outside `openspec/`. Keep inspection read-only and proportional to the change; reuse findings for later artifacts and inspect more only as needed.
        - Identify the target project from the request and project context; the planning home may be separate from the code. If the target is unclear, ask. For greenfield or non-code changes, inspect the available structure and relevant documents. If source is unavailable, state the limitation and ask when it materially affects the plan.
        - Ground scope, approach, and tasks in what you find. Distinguish observed behavior from assumptions and proposed additions; surface conflicts with existing specs instead of silently deciding which is correct.
        - Do this discovery now, rather than leaving generic "explore the codebase" or "make a plan" tasks for implementation. Keep any necessary follow-up investigation specific to an unresolved question.
      - Choose the output path before creating anything. If `resolvedOutputPath` is a glob, follow `instruction` to choose a concrete path inside `changeRoot` that matches the glob, and verify it remains inside `changeRoot` after resolving symlinks, both in its parent directories and in the file itself if it already exists; if it does not, stop and tell the user. Otherwise the output path is `resolvedOutputPath`
      - If the `instruction` field delegates creation to a specific skill or command, invoke it only if it can write the artifact to that output path; otherwise stop and tell the user. Then verify the artifact file exists at that output path
      - Otherwise create the artifact file using `template` as the structure and write it to that output path
      - Apply `context` and `rules` as constraints - but do NOT copy them into the file
      - Show brief progress: "✓ Created <artifact-id>"

   b. **Continue until every artifact in the required set exists (not just `apply.requires`)**
      - After creating each artifact, re-run `openspec status --change "<name>" --json`
      - The required set is `applyRequires` plus every artifact reachable from those by following the `requires` edges in `status --json` - walk them transitively (spec-driven closes over proposal, specs, design, tasks). Leave artifacts outside that set alone
      - `status` is file-existence only, so an `applyRequires` artifact reading `done` does NOT mean its dependencies exist - writing `tasks.md` early marks `tasks` done while `specs` was never written. Use each artifact's `requires` edges, not its `status`, to build the required set: a `done` artifact still lists what it depends on
      - An artifact already reading `status: "skipped"` is satisfied: the change declares `skip_specs` in `.openspec.yaml`, so its files must NOT exist. Never try to create one
      - Create every artifact in the required set that is missing, then re-check - creating one can unblock others
      - Skip one only when `status` already reports it `skipped`, or when its own `instruction` says it is conditional: run `openspec instructions <artifact-id> --change "<name>" --json` and skip only if its `instruction` field marks it optional (e.g. "create only if..."). Spec-driven's `design.md` qualifies; `specs` qualifies only via the `skipped` status above, never by your own judgment. Tell the user, and do not reconsider it
      - Dependencies are enablers, not gates: if a required artifact is still `blocked` only because you skipped a conditional dependency, write it anyway
      - Stop when every artifact in the required set is `done`, `skipped`, or was deliberately skipped

   c. **If an artifact requires user input** (critically unclear context):
      - Ask the user to clarify
      - Then continue with creation

5. **Show final status**
   ```bash
   openspec status --change "<name>"
   ```

**Output**

After completing all artifacts, summarize:
- Change name and location
- List of artifacts created with brief descriptions, plus any conditional artifact you skipped and why
- What's ready: "All artifacts needed for implementation are ready."
- Prompt: "Use the `/openspec-apply-change` skill 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 - it is the authoritative guidance, even for familiar artifact names
- If the `instruction` field directs you to use a specific skill or command to create the artifact, invoke it instead of writing the artifact directly - but only once you have chosen and checked the output path, and only if it can write there
- 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 every artifact the apply phase transitively depends on, not just the ids listed in `apply.requires`
- Always read dependency artifacts before creating a new one - re-read from disk, not from conversation memory (files may have changed since you last saw them)
- 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

© openspec · MIT · Fission-AI/OpenSpec

Похожие скиллы

Все скиллы по теме «Настройка агента: память, контекст, субагенты» →
openspec-context-loading forztf Скилл openspec-context-loading для Claude Code находит спецификации, изменения и требования в проекте и собирает готовую сводку для агента. Читает структуру OpenSpec напрямую. CX Codex +1 1 100установок 042-planning-openspec Juan Antonio Breña Moral Скилл 042-planning-openspec собирает артефакты OpenSpec — proposal, design, спецификации и задачи — из issue, плана или ADR. Полезен, когда требования уже есть, а разбить их на проверяемые изменения ещё нужно. CX Codex +1 330установок openspec-bootstrap sammcj Скилл openspec-bootstrap настраивает OpenSpec в репозитории: создаёт схему, конфигурацию и проверяет их. Нужен при первом запуске или изменении openspec/config.yaml. CX Codex +1 ★ 173звёзд репо openspec-implementation forztf Скилл openspec-implementation для Claude Code последовательно выполняет задачи утверждённых спецификаций OpenSpec, проверяя каждую тестами перед переходом дальше. CX Codex +1 1 400установок openspec itechmeat Скилл для работы с OpenSpec: объясняет артефактный граф, разрешение схем и шаблонов, жизненный цикл изменений и команды /opsx:. CX Codex +1 855установок oh-my-openspec Alexeyco Плагин oh-my-openspec ведёт разработку по спецификациям в Codex CLI: планирование, параллельные задачи и проверка OpenSpec через MCP-шлюз. CX Codex ★ 1 596звёзд репо

Из того же набора12

Весь набор →
openspec-propose Скилл openspec-propose для Claude Code создаёт полный пакет планирования OpenSpec за один шаг. Он формирует архитектурное решение, дельту спецификаций и задачи без изменения кода. CX Codex +1 4 600установок openspec-archive-change Скилл openspec-archive-change архивирует выполненные изменения спецификаций в экспериментальном цикле OpenSpec. Он проверяет готовность артефактов и задач перед фиксацией результата. CX Codex +1 4 500установок openspec-apply-change Скилл openspec-apply-change для Claude Code и других агентов запускает пошаговую реализацию задач из спецификации OpenSpec в кодовой базе. Берёт готовое изменение и выполняет пункты плана разработки. CX Codex +1 4 500установок openspec-explore Скилл openspec-explore для Claude Code переключает агента в режим думающего партнёра. Запускается, чтобы разобраться с задачей или уточнить требования до начала реализации. CX Codex +1 4 500установок openspec-onboard Проводит через полный цикл работы в OpenSpec, от выбора задачи до архивации изменений. Запускается по запросу «openspec onboard» или «opsx onboard». CX Codex +1 4 400установок openspec-bulk-archive-change Скилл openspec-bulk-archive-change для Claude Code и других платформ: архивирует несколько завершённых изменений OpenSpec за один раз. Закрывает параллельные задачи пачкой. CX Codex +1 4 400установок openspec-sync-specs Скилл openspec-sync-specs переносит дельта-спецификации из активного изменения OpenSpec в основные файлы требований без отправки задачи в архив. CX Codex +1 4 300установок openspec-verify-change Скилл openspec-verify-change сверяет написанный код со спецификациями, задачами и архитектурой OpenSpec перед архивацией изменения. Пригодится при финальной приёмке задач. CX Codex +1 4 000установок

Спонсоры проекта

Компании, которые помогают держать аналитику открытой