forge 0.13.14

A stable patch release. This page covers what changed since 0.13.13 (PRs #141 and #143). Both changes came from a repo where one feature routinely amends three specs at once: a semantic layer, its API routes and its UI.

One plan per change, not per spec

The planning skill said "one plan per subsystem." Agents took each per-system spec as a subsystem and wrote one plan per spec, so a feature crossing three specs became three plans built one layer at a time, even though the work goes back and forth between them.

• Planning: one plan per shippable change. Declare every touched spec in **Spec files:**, and a task may name sections from several specs ([api] Routes, [ui] Dashboard). Split plans only when a piece works and ships on its own.
• Brainstorming: the scope check decomposes only into pieces that ship on their own. Touching several specs is not decomposition.

The tooling has supported multi-spec plans since 0.13.4; only the skill text lagged behind.

Spec review checks the spec under review (#142)

Spec lint ran only on specs a plan declared. A spec whose system id didn't match its filename passed spec review and every single-spec plan, then failed mid-plan the first time a multi-spec plan declared it.

• forge_docreview.py --spec now runs the living-spec lint rules on the reviewed spec before building the packet or validating a verdict. Any defect stops the run and lists every problem.
• Only that spec is checked. Old drift elsewhere in docs/forge/specs/ doesn't block unrelated reviews.
• To find existing drift in a repo, run forge_lint.py --specs once from its root.

Codex

No hooks/hooks.json change since 0.13.13, so Codex doesn't ask you to re-trust forge's hooks.

Install

claude plugin marketplace update forge
claude plugin update forge@forge        # or: claude plugin install forge@forge

Restart the session to apply. On Codex: codex plugin marketplace add forcetrainer/forge --ref forge--v0.13.14, then codex plugin add forge@forge.