Skip to content

v1.6.0

Choose a tag to compare

@github-actions github-actions released this 16 May 03:48
· 105 commits to main since this release
Immutable release. Only release title and notes can be modified.

What's changed in v1.6.0

Features

  • Upgrade adoption flow (review-upgrade + reconcile) (#254)

Adoption guide

These prompts help your AI agent adopt the new features in an existing project. Copy them into your harness, or run @specflow-expert review-upgrade to be walked through automatically.

#254 — Upgrade adoption flow (review-upgrade + reconcile)

specflow reconcile is a new top-level subcommand and specflow-expert review-upgrade is a new agent mode. Existing projects that documented the upgrade workflow in their agent files should reference both. Projects that don't already mention upgrade conventions in their agent files can ignore — Specflow's own specflow-expert.md already covers this in fresh scaffolds and existing projects will pick it up on the next specflow upgrade.

Audit my project for any agent files (`.claude/agents/*.md`, equivalent Cursor / Codex / Windsurf rule files, AGENTS.md, CLAUDE.md) that document the `specflow upgrade` workflow. Update them to mention:

1. After `specflow upgrade`, the CLI prints a handoff to `@specflow-expert review-upgrade`.
2. `specflow reconcile --status` lists files pending post-upgrade reconciliation.
3. `specflow reconcile <path> --accept-upstream` takes the new template version (backs up local to `<path>.specflow.bak`); `--accept-current` keeps the local version (re-stamps the lock SHA only).

Open a PR. Skip projects that don't currently document the upgrade flow — no proactive scaffold change required.

🤖 Generated with Claude Code

Internal / chores

1 internal change
  • Upgrade adoption flow — design + implementation plan (#253)

Full changelog: v1.5.0...v1.6.0