mcpField
O
openspec-ff

openspec-ff

github.com/full-stack-skillsAgent workflows188 installsUpdated 4w ago
Repository

About openspec-ff

openspec-ff is an OpenSpec skill for generating a change’s planning artifacts in one pass. It suits users with a clear feature scope who want proposal, specs, design, and tasks created in dependency order.

Key features

  1. 01Generate planning artifacts in one pass
  2. 02Create artifacts in dependency order
  3. 03Support a specified change

Use cases

  1. 01Draft plans for a well-defined feature
  2. 02Create all planning documents without incremental review

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-ff

After installing, type/openspec-ffin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

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

Comments

Markdown supported