Overplane 0.0.8 is a spec-workflow release: overplane spec new grew a
proper inline body editor, spec frontmatter lost two fields nobody was
using well, and plain build output went from quiet to silent-until-summary.
The README also got a live screencast, which changes nothing about the
binary but does make us look busier.
What you get
- Write the whole spec in one sitting. The
spec newinteractive form
now ends with a multi-line body editor (Enter inserts newlines,
Ctrl+S or Alt+Enter finishes), so you no longer bounce out to$EDITOR
to write the actual spec. Leave it empty and you get the starter
skeleton, same as before. - Leaner spec frontmatter. The
statusandauthorfields are gone
from the spec-metadata schema, along with the--statusand--author
flags onspec new. Builds no longer skip specs by status: every spec
in the directory builds. - Silent plain build output. Plain-mode
overplane buildno longer
prints per-step progress lines; you get the log stream and the final
Build Summary table. Use--tuito watch progress live. - Clearer next steps. After
spec new, the next-step table points you
atoverplane build allinstead of a manual edit-and-validate loop. - A prose sweep across help text, prompts, and docs: em-dashes and
AI-cliche phrasing removed, so the CLI reads like a person wrote it.
What you need to do
- Upgrade:
overplane upgrade 0.0.8, ornpm install -g overplane, or
grab a binary below. - Migration: if existing spec files carry
status:orauthor:in
their frontmatter, delete those lines; strict validation now rejects
unknown fields. Scripts passing--status,--author, or--editto
spec newmust drop those flags.
Under the hood
Imported from go-core since v0.0.7: a reusable multiline form primitive in
the TUI platform layer (FormText / RunMultilineForm with a custom huh
keymap, since terminals cannot distinguish Ctrl+Enter from Enter); the
plain build presenter deleted in favor of the noop presenter now that the
summary table carries the result; the spec-metadata schema slimmed and its
drift tests updated; the npm-publish workflow copies the root README into
the npm package at release time; and the public README hero swapped from a
GIF to a webm screencast of a real build.
Assets are bare executables (upx-packed where supported), not tarballs:
download the one for your platform, chmod +x it (unix), and run it.
Verify the artifacts
sha256sum --ignore-missing -c checksums.txt
cosign verify-blob \
--certificate checksums.txt.pem \
--signature checksums.txt.sig \
--certificate-identity-regexp 'https://github.com/overplane/overplane' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
checksums.txt