v0.25.0¶
Release Date: 2026-11-11
Highlights¶
- OGSM joins OKR, V2MOM, and VSEM in
goals.goals/ogsmmodels OGSM (Objective, Goals, Strategies, Measures) plans: one objective in words, goals in numbers that say it has been reached, the strategies that reach them, the measures that track each strategy, and the actions that carry the strategies out. It comes with validation presets, Markdown and Marp renderers, a generated JSON Schema, and asplan goals ogsmcommand.
Overview¶
An OGSM puts a plan on one page, two parts in words and two in numbers. Goals measure the objective and move slowly; measures track each strategy and move within weeks, so they say early whether a strategy is working. OGSMs cascade: a strategy at one level becomes the objective of the level below.
See the OGSM guide.
Changes¶
goals/ogsm¶
OGSM,Metadata,Objective,Goal,Strategy,Measure, andAction, withNew,ReadFile,Parse, andWriteFile.- Strategies name the goals they serve; measures and actions name their strategy.
Goal,Strategy,StrategiesFor,MeasuresFor, andActionsForread the plan. - Cascading:
metadata.parentIdnames the parent OGSM, andobjective.parentStrategyIdthe parent strategy the objective carries out. Validatewith two presets. Structural problems are always errors: no objective, goals, or strategies, a missing or duplicate ID, an unknown goal, strategy, or action, an unknown status, priority, or direction, and a bad date. Missing targets, owners, the objective's due date, measures, actions, and links between goals and strategies are warnings underDefaultValidationOptionsand errors underStrictValidationOptions, which also warns at more than five goals or five strategies.- Renderers in
goals/ogsm/render/markdown(a document that opens with the classic one-page table: objective, goals, strategies, and measures side by side) andgoals/ogsm/render/marp(slides). Both produce the same bytes for the same plan.
goals¶
goals.FrameworkOGSM, goals.NewOGSM, and Goals.IsOGSM add OGSM to the union. An OGSM's strategies are its goal items, and its goals and then its measures its result items, labelled "Strategies" and "Goals and Measures". A goal has no GoalID, since it measures the objective.
splan¶
splan goals ogsmhasvalidate(with--strict),generate markdown,generate marp(with--theme), andinit. The template meets the strict options, with its objective due three years from today.splan goals validatedetects an OGSM from its singleobjective, andsplan goals init --frameworkandsplan schema generate --typeacceptogsm.- The goals command generators share one read-and-render helper.
Schema¶
schema/ogsm.schema.json is generated from the OGSM types and embedded as schema.OGSMSchema() and schema.OGSMSchemaBytes(). The PRD schema is regenerated because it embeds the goals union, which now has an ogsm option.
Examples¶
examples/minimal.ogsm.json and examples/product.ogsm.json, a fictional bookkeeping app's three-year plan, are checked to validate. The full example also meets the strict options.
Documentation¶
- An OGSM guide covering the four parts, cascading, how OGSM differs from VSEM and V2MOM, validation, goals alignment, rendering, and the command line.
- OGSM in the README, the goals overview, the documentation home, the API reference, and the getting-started pages.
Compatibility¶
Additive only. An API comparison against v0.24.0 reports the new goals, schema, and cli identifiers as compatible changes, and no incompatible changes. JSON written by v0.24.0 reads unchanged.