Skip to content

Changelog

  • Flow-Next 1.1.4 makes ## Acceptance Criteria the canonical spec heading
  • Acceptance criteria parsing remains tolerant of legacy ## Acceptance and lowercase ## Acceptance criteria
  • Flow-Next 1.1.3 aligns cross-spec plan-sync on planSync.crossSpec
  • Repo-root SPEC.md / spec.md template discovery for project-customized spec scaffolds
  • /flow-next:setup can opt into a root SPEC.md without clobbering custom templates
  • Spec vocabulary stabilized in 1.0
  • Symmetric --scope=business|technical|both interview
  • Source-tagged capture with mandatory read-back
  • PR-as-cognitive-aid generation
  • Agent-native memory audit and migration
  • PR feedback resolver
  • Strategy and glossary grounding
  • Ralph autonomous mode with receipts

The canonical changelog lives in the Flow-Next repository:

github.com/gmickel/flow-next

Use this page to explain release highlights for humans:

  • new slash commands
  • changes to spec or task semantics
  • review receipt changes
  • migration requirements
  • breaking or deprecated behavior
  • docs, team workflow, or Ralph changes that alter how people should work

The repository changelog remains canonical. This page should summarize the current public story, not duplicate every commit.

Use ## Acceptance Criteria in new specs and examples. Flow-Next still parses legacy ## Acceptance and ## Acceptance criteria headings so existing specs do not need a migration.

flowchart LR
  Change["Behavior change"] --> Docs["Update docs"]
  Change --> Tests["Run tests"]
  Docs --> Changelog["Update changelog"]
  Tests --> Release["Cut release"]

If Flow-Next behavior changes and the docs site does not change, assume the release is incomplete until proven otherwise.