Skip to content

v0.23.0

Release Date: 2026-11-11

Highlights

  • VSEM joins OKR and V2MOM in goals. goals/vsem models VSEM (Vision, Strategy, Execution, Metrics) plans: a vision or mission, the strategies that will reach it and the resources each commits, the initiatives, programs, and actions that carry each strategy out, and metrics that each name the person accountable for them. It comes with validation presets, Markdown and Marp renderers, and a generated JSON Schema.

Overview

VSEM puts a plan on one page. Where V2MOM adds values and obstacles, VSEM adds what V2MOM leaves out: the resources each strategy commits, the work kept apart from the strategy it serves, and an owner for every metric. VSEM has no single canonical source, so the package documents the form it follows. A PRD or roadmap can carry a VSEM through the framework-agnostic goals union, as it carries OKRs or a V2MOM.

See the VSEM guide.

Changes

goals/vsem

  • VSEM, Metadata, Strategy, Resource, Execution, and Metric, with New, ReadFile, Parse, and WriteFile.
  • Execution items and metrics name their strategy by ID. A metric without a strategy measures the vision as a whole. Strategy, ExecutionFor, MetricsFor, VisionMetrics, and Statement (the vision, or the mission when there is no vision) read the plan.
  • Validate with two presets. Structural problems are always errors: a missing vision and mission, a missing ID or name, a duplicate ID, an unknown strategy or dependency, an unknown status, kind, priority, or direction, and a bad date. Gaps in ownership and coverage, such as a metric without an owner or a target, or a strategy with no work, no metric, or no resources, are warnings under DefaultValidationOptions and errors under StrictValidationOptions.
  • Renderers in goals/vsem/render/markdown (a document) and goals/vsem/render/marp (slides: the plan on one page, the vision, a slide per strategy, and the vision's metrics). Both produce the same bytes for the same plan.

goals

goals.FrameworkVSEM, goals.NewVSEM, and Goals.IsVSEM add VSEM to the union. A VSEM's strategies are its goal items and its metrics its result items, labelled "Strategies" and "Metrics", so ToSwimlaneTableWithGoals and other framework-agnostic code work with it unchanged.

Schema

schema/vsem.schema.json is generated from the VSEM types and embedded as schema.VSEMSchema() and schema.VSEMSchemaBytes(). The PRD schema is regenerated because it embeds the goals union, which now has a vsem option.

Examples

examples/minimal.vsem.json and examples/product.vsem.json, a fictional bookkeeping app's plan, are checked to validate. The full example also meets the strict options.

Fixed

Releases publish their binaries again. GoReleaser still targeted the repository's former name; GitHub redirects that address, but asset uploads do not follow the redirect, so v0.22.0 was published without binaries. The release workflow now also takes its Go version from go.mod and pins GoReleaser v2.

Documentation

  • A VSEM guide in the goals section.
  • The README, the documentation home, the goals overview, the API reference, and the getting-started pages list VSEM beside OKR and V2MOM. The overview compares the three, and the README's goals example now compiles.
  • Examples use the github.com/grokify/prism-roadmap module path. The CI example installs splan, validates with splan requirements prd validate, and gates on splan requirements prd score.

Dependencies

  • github.com/spf13/pflag v1.0.10 → v1.1.0 (indirect)
  • golang.org/x/oauth2 v0.37.0 → v0.38.0 (indirect)
  • golang.org/x/sync v0.24.0 → v0.25.0 (indirect)
  • golang.org/x/sys v0.49.0 → v0.50.0 (indirect)

Compatibility

Additive only. An API comparison against v0.22.0 reports the new goals and schema identifiers as compatible changes, and no incompatible changes. JSON written by v0.22.0 reads unchanged.

Installation

go get github.com/grokify/prism-roadmap@v0.23.0