Repository navigation
v7.2.0
What's changed in v7.2.0
Highlights
One unit of work, one address: /task. The backlog (list, next, add, edit, close,
groom), the delivery pipeline (plan → tasks → implement → review → merge), audits
(/task audit --security|--archi|--perf|--a11y|--deps, every applicable axis with no flag) and
constitution now live under one skill. /specnaut documents the framework (doc, list,
upgrade), /ship is unchanged. /board, /code-audit and the five *-audit skills are retired,
with no aliases: /specnaut plan names its new address and stops. specnaut upgrade carries your
edited phase documents and your addenda to their new address, and never overwrites or follows a link
to do it. Skill descriptions loaded in every session shrink by about a third on Claude Code and
almost half on Codex.
Rules that must hold are hooks, on Claude Code and Codex. Under merge: manual, a merge into
the base branch really waits for your go-ahead; a Specnaut agent runs on the model its definition
declares; installed.lock cannot be hand-edited; on Codex, publishing a release needs your go-ahead
in the same turn. On Codex, trust the hooks once with /hooks after upgrading.
See UPGRADING.md for what moved.
Features
- Regroup the bundled skills into specnaut, task and ship
- Upgrade carries moved docs and addenda without losing a byte
- Must-hold rules are hooks on Claude Code and Codex
Bug fixes
- The tag-release smoke reads the retired-addresses table
- Hooks survive a CRLF checkout and doubled slashes on Windows
- Hooks and their tests on Windows
- Gen-hooks resolves its root with fromFileUrl
- Gate a git alias set inline with -c
Adoption guide
These prompts help your AI agent adopt the new features in an existing project. Copy them into your harness, or run @specnaut-guide review-upgrade to be walked through automatically.
Regroup the bundled skills into specnaut, task and ship
After `specnaut upgrade`, use `/task` where you used `/board`,
`/specnaut plan|tasks|implement|review|merge|constitution`, `/code-audit` or
an `*-audit` skill (`/board update` is `/task edit`; `/sec-audit` is
`/task audit --security`, and so on). On Codex the skill is `specnaut-task`.
Search this project's own prompts, skills and AGENTS.md prose for the old
addresses and offer to update them. Under `merge: manual`, the merge
go-ahead is now `/task merge` (Codex: `/specnaut-task merge`). On Codex, the
hooks changed: tell the user to run /hooks and trust them again. Update the
Claude Code plugin together with the binary.
Upgrade carries moved docs and addenda without losing a byte
Run `specnaut upgrade`. It moves this project's Specnaut pipeline from
/specnaut to /task: edited phase documents travel to their new address, and
addenda under .specnaut/addenda/specnaut/<phase>.md move to
.specnaut/addenda/task/<phase>.md. If the report warns that an addendum or a
document could not move (a link, or a file already at the new address),
show the user both paths and offer to merge them. If it names a customised
specnaut/SKILL.md, tell the user it no longer routes the pipeline and offer
to carry their change into an addendum.
Must-hold rules are hooks on Claude Code and Codex
Run `specnaut upgrade`. The hook scripts move from .claude/hooks/ to
.specnaut/hooks/ and their .claude/settings.json entries are rewritten in
place; the user's own hooks stay. If the report keeps an old
.claude/hooks/protect-generated.sh or log-subagent.sh because it was
customized, tell the user nothing runs it any more and offer to carry the
change into .specnaut/hooks/. On Codex, tell the user to open Codex in the
project, run /hooks and trust Specnaut's hooks — until then none of the
must-hold rules runs there. If the project uses `merge: manual`, explain
that a landing on the base branch now needs their go-ahead: Claude asks; on
Codex they type `merge` (or `/specnaut merge`) in the turn that merges.
Internal / chores
6 internal changes
Full changelog: v7.1.0...v7.2.0