ff

Fast-Forward — Create All Planning Artifacts (Expanded Workflow)

You are fast-forwarding through the artifact pipeline, creating all remaining planning artifacts for an active change in topological dependency order.

Note: This is part of the expanded workflow. This is equivalent to running /openspec:continue repeatedly until all planning artifacts are done.

Upstream source: Fission-AI/OpenSpec

Workflow

Step 1: Identify Active Change

• If the user specified a change name, use that
• Otherwise, find the change in openspec/changes/ with a .openspec.yaml and incomplete artifacts
• If multiple changes are active, list them and ask which to fast-forward

Step 2: Assess Current State

Check which artifacts exist and which need to be created (same state assessment as /openspec:continue):

Change: [change-name]
Schema: spec-driven

Current state:
  ✓ proposal.md   — DONE (exists)
  ⋯ specs/        — MISSING (will create)
  ⋯ design.md     — MISSING (will create)
  ⋯ tasks.md      — MISSING (will create)

Fast-forwarding: will create specs/, design.md, tasks.md

If all artifacts already exist, report that nothing needs to be done.

Step 3: Create Artifacts in Dependency Order

Generate each missing artifact in topological order (respecting dependencies):

For the spec-driven schema: proposal → (specs, design in parallel) → tasks

Step 3a: Create proposal.md (if missing — no scaffold yet) Create a proposal document (see /openspec:new and /openspec:continue for full instructions).

Step 3b: Create specs/ (if proposal.md exists) Create specification files for each capability listed in proposal.md. See /openspec:continue for spec format.

Step 3c: Create design.md (if proposal.md exists) Create a technical design document. See /openspec:continue for design format.

Step 3d: Create tasks.md (after specs/ and design.md are done) Create the implementation task checklist, referencing all available artifacts. See /openspec:continue for tasks format.

After creating each artifact, briefly report:

✓ Created: specs/[capability]/spec.md
✓ Created: design.md
✓ Created: tasks.md

Step 4: Final Summary

Fast-Forward Complete: openspec/changes/[change-name]/

  Created:
    ✓ specs/[capability]/spec.md  — [N] requirements, [N] scenarios
    ✓ design.md                   — [N] key decisions
    ✓ tasks.md                    — [N] implementation tasks

  Planning is complete. Ready to implement.

Next step: Run /openspec:apply to start implementing the tasks.

Notes

• This is equivalent to running /openspec:continue multiple times
• Use /openspec:continue instead if you want to review each artifact before creating the next
• If any artifact already exists, it will not be overwritten — fast-forward only creates missing artifacts
• After fast-forward, use /openspec:apply to implement the tasks