Versioning

Flow-Next 1.x stabilizes the spec vocabulary.

1.0 rename

epic became spec.

• flowctl epic * aliases flowctl spec *
• flowctl epics aliases flowctl specs
• --epic aliases --spec
• /flow-next:epic-review aliases /flow-next:spec-completion-review

Aliases emit deprecation warnings through 1.x. Removal target is 2.0, telemetry-driven.

Repo migration

flowctl migrate-rename --yes
flowctl migrate-rollback --yes

Interactive path:

/flow-next:setup

Compatibility promise

Within 1.x:

• spec is the canonical term.
• Legacy epic aliases continue as warnings, not preferred docs language.
• R-ID semantics remain stable.
• Repo-local .flow/ state should migrate forward without losing tracked work.
• Pure docs and agent guidance changes do not require plugin version bumps.

Docs and changelog

Behavior changes should update:

• relevant docs page
• command reference if user-facing command behavior changes
• changelog entry
• examples or screenshots when UI/copy changes

This site should stay in sync with the Flow-Next plugin repo, including new docs such as teams, Ralph, and flowctl references.