openspec-ff

Fast-forward through artifact creation with `/opsx:ff`, generating all planning artifacts (proposal, specs, design, tasks) at once. Use when the user says "fast forward", "create all artifacts", "/opsx:ff", or has a clear picture of what to build.

261 stars

Best use case

openspec-ff is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Fast-forward through artifact creation with `/opsx:ff`, generating all planning artifacts (proposal, specs, design, tasks) at once. Use when the user says "fast forward", "create all artifacts", "/opsx:ff", or has a clear picture of what to build.

Fast-forward through artifact creation with `/opsx:ff`, generating all planning artifacts (proposal, specs, design, tasks) at once. Use when the user says "fast forward", "create all artifacts", "/opsx:ff", or has a clear picture of what to build.

Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.

Practical example

Example input

Use the "openspec-ff" skill to help with this workflow task. Context: Fast-forward through artifact creation with `/opsx:ff`, generating all planning artifacts (proposal, specs, design, tasks) at once. Use when the user says "fast forward", "create all artifacts", "/opsx:ff", or has a clear picture of what to build.

Example output

A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.

When to use this skill

  • Use this skill when you want a reusable workflow rather than writing the same prompt again and again.

When not to use this skill

  • Do not use this when you only need a one-off answer and do not need a reusable workflow.
  • Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/openspec-ff/SKILL.md --create-dirs "https://raw.githubusercontent.com/partme-ai/full-stack-skills/main/skills/openspec-skills/openspec-ff/SKILL.md"

Manual Installation

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

How openspec-ff Compares

Feature / Agentopenspec-ffStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Fast-forward through artifact creation with `/opsx:ff`, generating all planning artifacts (proposal, specs, design, tasks) at once. Use when the user says "fast forward", "create all artifacts", "/opsx:ff", or has a clear picture of what to build.

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.

Related Guides

SKILL.md Source

# OpenSpec Fast-Forward Skill

Use **`/opsx:ff`** to fast-forward through all planning artifact creation at once. Creates all artifacts in dependency order (proposal -> specs -> design -> tasks) in a single pass.

## When to Use

- The user has a clear picture of what to build and does not need incremental review.
- The user says "fast forward", "create everything", "generate all planning docs".
- Small to medium features where step-by-step review is unnecessary.

## Prerequisites

- **An active change** exists (created via **openspec-new** or `/opsx:new`).
- Or use `/opsx:ff <change-name>` to create and fast-forward in one step.

## Workflow

1. **Run fast-forward**
   - `/opsx:ff` — fast-forward the current/inferred change.
   - `/opsx:ff <change-name>` — fast-forward a specific change.

2. **Artifacts are created in dependency order**
   - In the default `spec-driven` schema:
     1. `proposal.md` — why and what
     2. `specs/**/*.md` — delta specs (requirements and scenarios)
     3. `design.md` — technical approach
     4. `tasks.md` — implementation checklist
   - Each artifact reads its dependencies before being created.

3. **Review**
   - All planning artifacts are now available. The user can edit any of them before proceeding.

## Outputs

- All planning artifacts created in `openspec/changes/<name>/`:
  - `proposal.md`
  - `specs/**/*.md`
  - `design.md`
  - `tasks.md`

## Next Steps

- Review and edit artifacts if needed.
- Use **openspec-apply** to implement tasks.
- Or use **openspec-verify** after implementation to validate.

## Troubleshooting

- **"Change not found"**: Specify the name: `/opsx:ff add-dark-mode`.
- **Artifact quality issues**: Use `/opsx:continue` instead for more control; add project context in `openspec/config.yaml` (see **openspec-config**).

## References

- [OpenSpec Commands: /opsx:ff](https://github.com/Fission-AI/OpenSpec/blob/main/docs/commands.md)

Related Skills

openspec-verify

261
from partme-ai/full-stack-skills

Validate that implementation matches change artifacts using `/opsx:verify`, checking completeness, correctness, and coherence. Use when the user says "verify implementation", "check my work", "/opsx:verify", or wants quality validation before archiving.

openspec-update

261
from partme-ai/full-stack-skills

Run `openspec update` to regenerate AI tool instruction files after upgrading the OpenSpec CLI. Use when the user says "update OpenSpec", "openspec update", or "refresh OpenSpec skills/commands".

openspec-sync

261
from partme-ai/full-stack-skills

Sync delta specs from a change into main specs using `/opsx:sync`, without archiving the change. Use when the user says "sync specs", "merge specs to main", "/opsx:sync", or needs to update main specs mid-change.

openspec-schema

261
from partme-ai/full-stack-skills

Create and manage custom workflow schemas using `openspec schema init/fork/validate/which`. Use when the user says "create a custom workflow", "custom schema", "fork a schema", or wants to define their own artifact types and dependencies.

openspec-onboard

261
from partme-ai/full-stack-skills

Guided onboarding through the complete OpenSpec workflow using `/opsx:onboard`, walking the user through a real change in their codebase. Use when the user says "onboard me", "tutorial", "/opsx:onboard", "how does OpenSpec work", or is new to OpenSpec.

openspec-new

261
from partme-ai/full-stack-skills

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

openspec-install

261
from partme-ai/full-stack-skills

Install the OpenSpec CLI globally via npm, pnpm, yarn, bun, or nix. Use when the user says "install OpenSpec", "set up OpenSpec", or "openspec command not found".

openspec-initial

261
from partme-ai/full-stack-skills

Run `openspec init` to initialize OpenSpec in a project directory, creating the openspec/ folder structure and configuring AI tool integrations. Use when the user says "initialize OpenSpec", "openspec init", or "set up OpenSpec in this project".

openspec-explore

261
from partme-ai/full-stack-skills

Think through ideas, investigate problems, and clarify requirements before committing to a change using `/opsx:explore`. Use when the user says "explore an idea", "think through this", "investigate options", or wants to brainstorm before creating a formal change.

openspec-continue

261
from partme-ai/full-stack-skills

Create the next artifact in the dependency chain with `/opsx:continue`, building up a change incrementally. Use when the user says "continue the change", "create next artifact", "/opsx:continue", or wants step-by-step artifact creation.

openspec-config

261
from partme-ai/full-stack-skills

Configure OpenSpec project settings and global CLI configuration using `openspec/config.yaml` and `openspec config` commands. Use when the user says "configure OpenSpec", "project config", "add project context", or wants to set per-artifact rules.

openspec-bulk-archive

261
from partme-ai/full-stack-skills

Archive multiple completed changes at once with `/opsx:bulk-archive`, handling spec conflicts between changes. Use when the user says "archive all changes", "bulk archive", "/opsx:bulk-archive", or has multiple completed changes.