Repository navigation
0.13.0 - 2026-09-30
Release Notes
Added
- (landing) [breaking] Render seeds for their root and lint through discovery
What this release asks of an instance
- The three managed files under
.spec-driven-docs/markdownlint/are retired, and<root>/.markdownlint-cli2.jsoncis the new managed file. An instance that edited one of the three restores the recorded bytes before the upgrade, because the upgrade refuses while the edit stands. - A root
.markdownlint-cli2.jsoncis seeded to load the relative-links rule, only where the root holds no markdownlint configuration of either family. Where one exists, the seed yields and the setup skill proposes the loader. - The rendered hook block replaces the
md-spec,md-adr, andmd-relative-linkshooks with onemarkdownlint-cli2hook that reads configuration through discovery. - relative-links now judges every relative link outside the decision records, and MD040 judges fences under the documentation root.
- The rendered
AGENTS.mdblock ends each item with a line-local MD013 suppression, which an upgrade writes inside the markers only. A createdAGENTS.mdopens with a# AGENTStitle. - New rule IDs:
staging:a-seed-lands-rendered-for-its-root,instance:the-lint-configuration-composes,docs-specs:a-spec-follows-the-heading-shape, anddecision-records:a-record-follows-the-heading-shape. SPEC-tracking.md,SPEC-docs-specs.md, andSPEC-decision-records.mdare reworded. An instance reconciles them by readingsdd spec <domain>.sdd verifyfails on a.markdownlint.*file at the documentation root, and on any markdownlint configuration beneath itsspecs/ordecisions/directory.
Install spec-driven-docs 0.13.0
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/gubasso/spec-driven-docs/releases/download/v0.13.0/spec-driven-docs-installer.sh | shDownload spec-driven-docs 0.13.0
| File | Platform | Checksum |
|---|---|---|
| spec-driven-docs-x86_64-unknown-linux-gnu.tar.xz | x64 Linux | checksum |
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo gubasso/spec-driven-docsYou can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>