v0.20.0

[0.20.0] - 2026-07-16

New Features

• Publish a spec to JIRA with the new specship_jira_publish tool: it creates a Story whose Sub-tasks mirror the spec's acceptance criteria, records the issue key in the spec so branches, PRs, and tracking pick it up automatically, and is safe to re-run (it updates the existing Story instead of duplicating it). After authoring a spec with JIRA connected, SpecShip now offers this in one prompt.
• Commits for a JIRA-backed spec are prefixed with the issue key (PROJ-123: …), so JIRA's development panel and smart commits link them to the issue.
• Verifying an acceptance criterion now advances its published JIRA Sub-task toward Done (and the Story once every Sub-task is done), and a spec that drifts posts a one-time comment on its issue — both configurable via the SPECSHIP_JIRA_TRANSITION_DONE and SPECSHIP_JIRA_PROJECT settings.
• New specship jira release <version> command stamps a released version onto your JIRA issues as fixVersion with a shipped-in comment, creating the project version if needed; re-running it is a no-op.
• When no publish project is set, SpecShip now shows the JIRA projects your account can access and lets you choose — interactively during specship jira configure (or via its new --project flag), and as a pick-list when publishing a spec.
• specship_jira_track now also lists published specs and flags issues that were edited in JIRA after publishing, so specs and their JIRA mirrors can't silently diverge.
• New specship jira transition <key> [state] command (and a specship_jira_transition tool) move a JIRA issue to any state its workflow offers — or list the available transitions when you omit the state. A state the workflow can't reach is reported with the options instead of applied, so nothing is written by mistake.
• specship jira test now checks your configured lifecycle transition names (In Progress / In Review / Done) against your live JIRA workflow and flags any it can't fire, so a workflow that lacks (say) an "In Review" state surfaces up front instead of silently skipping when a run completes.
• New specship memory commands let you teach SpecShip from mistakes: memory capture records a lesson or anti-pattern as a reviewable memory rule — targeting a portable ~/.claude memory note or your project CLAUDE.md — so a mistake you don't want repeated gets loaded into the next session; memory list shows the memory rules SpecShip has applied; and memory remove / memory edit take an item down or revise its body, each previewed before it's written. Human-gated and reversible like every reflection change: nothing is written until you confirm.

Fixes

• Verified and broken spec links no longer silently reset to unverified when a spec is re-extracted for an unrelated reason (for example, appending another requirement to the same spec file) — a link's verdict is now preserved as long as the requirement's own text hasn't changed. Editing the requirement itself now flags its links as drifted (so they show up for re-verification) instead of quietly dropping the verdict.