v0.24.0¶
Release Date: 2026-11-11
Highlights¶
- MEL plans in
goals/mel. A monitoring, evaluation, and learning plan in one validated document: a results framework from outputs to impact, the activities that produce it, an indicator reference sheet per indicator, the assumptions to monitor, an evaluation plan, a learning agenda, and a review and reporting schedule. It comes with validation presets, Markdown and Pandoc renderers, and a generated JSON Schema. splan goalsworks with every goal framework.goals validateandgoals inithandle OKR, V2MOM, VSEM, DMAIC, and MEL, and newgoals vsem,goals dmaic, andgoals melsubcommands validate, render, and create each format.
Overview¶
A MEL plan says how a team will know whether its work is producing the results it intends, and what it will do with what it learns. Monitoring tracks indicators continuously; evaluation asks, at set times, whether and why results happened; learning turns both into decisions. MEL plans are common in program work and just as useful for a product or business team: the full example is the onboarding plan of a fictional bookkeeping app.
See the MEL guide.
Changes¶
goals/mel¶
Plan,Metadata,Result,Activity,Indicator,Baseline,Target,DataQuality,Assumption,Evaluation,LearningQuestion,Review, andReport, withNew,ReadFile,Parse, andWriteFile.- Results sit at five levels (
output,short_term,medium_term,long_term,impact) and name the results they contribute to.TopResults,Contributors,ActivitiesFor, andIndicatorsForread the framework. - An indicator
measuresa result, an activity whose delivery it tracks, or an assumption it watches. Its reference sheet holds the definition, type, unit, direction, disaggregation, baseline, targets, data source, collection method, frequency, owner, and data quality checks and limitations. - Evaluations have questions, a type (
baseline,process,formative,midterm,final,impact,developmental), a method, an evaluator, and dates. Learning questions have the decision each informs, how and by when it will be answered, and what it bears on. Reports say what each audience needs to know, what it receives, and how often. Validatewith two presets. Structural problems are always errors: a missing or duplicate ID, an unknown reference or one to the wrong kind of element, a cycle in the results framework, an unknown value, or a bad date. Gaps in the collection plan, evaluation plan, learning agenda, and schedule are warnings underDefaultValidationOptionsand errors underStrictValidationOptions.- Renderers in
goals/mel/render/markdownandgoals/mel/render/pandoc(with front matter for a PDF). The results framework is drawn as a nested list from impact down, and a result shared by several branches is drawn once.SummaryOptionsleaves out the reference sheets. Both produce the same bytes for the same plan.
splan goals¶
splan goals validate FILEvalidates any goal document with its framework's own rules. The framework is detected from the file's fields, or given with--framework, and--stricttreats gaps as errors. It previously checked OKR files only, with a few rules of its own.splan goals init --frameworkcreates a template forokr,v2mom,vsem,dmaic, ormel.splan goals vsem,goals dmaic, andgoals meleach havevalidate(with--strict),generate(VSEM asmarkdownormarp, DMAIC asmarporpandoc, MEL asmarkdownorpandocwith--summary), andinit. The VSEM, DMAIC, and MEL templates meet their strict options.- In Go,
cli.ValidateGoals,cli.DetectGoalFramework, and theVSEMTemplate,DMAICTemplate, andMELTemplatefunctions.
Schema¶
schema/mel.schema.json is generated from the MEL types and embedded as schema.MELSchema() and schema.MELSchemaBytes(). splan schema generate --type accepts vsem, dmaic, and mel as well as prd, okr, and v2mom.
Examples¶
examples/minimal.mel.json and examples/product.mel.json are checked to validate; the full example also meets the strict options.
Documentation¶
- A MEL guide in the goals section.
- The README lists the goals commands, and the VSEM, MEL, and DMAIC guides show their command lines.
- The canvas overview links the README's templates catalog on GitHub, so the strict documentation build passes.
Dependencies¶
github.com/spf13/pflagv1.1.0 is now a direct dependency, used by the CLI tests.
Compatibility¶
Additive for Go callers. An API comparison against v0.23.0 reports the new schema and cli identifiers as compatible changes, and no incompatible changes. On the command line, splan goals validate now applies each framework's full rules, so an OKR file that passed its earlier checks may report findings it did not before.