Skip to content

v0.15.0 Release Notes

Release Date: 2026-08-03

This release moves VisionSpec's workflow definitions to their canonical home: specification-workflow-spec now owns all 24 default workflows — configurations, templates, and rubrics — and VisionSpec consumes them as embedded Go data through composable loaders. VisionSpec's local pkg/profiles package and its duplicated profile directories are retired.

Highlights

  • Canonical workflow library: all 24 default workflows (stage-based, methodology, big-tech syntheses, v2mom, pbhq-lite) load from specification-workflow-spec v0.2.0 with no filesystem access
  • One loading path: embedded defaults, organization directories, and extends inheritance all resolve through specification-workflow-spec's composable loaders (file, chain, resolving)
  • Bridge helpers: templates.LoaderForWorkflow, rubrics.LoaderForWorkflow, and types.SpecConfigFromWorkflow feed VisionSpec's existing interfaces from a loaded workflow — rubrics flow through as structured-evaluation RubricSet with no conversion
  • New pbhq-lite workflow: minimal PRD/TRD/PLAN/ROADMAP workflow for internal initiatives

Breaking Changes

  • pkg/profiles is removed. Workflow definitions, templates, and rubrics live in specification-workflow-spec; load them via workflows.DefaultLoader() and the bridge helpers.
  • Go API renames: cli.ConfigFromProfile is now cli.ConfigFromWorkflow, cli.Config.ProfileLoader is now cli.Config.WorkflowLoader (a specification-workflow-spec workflows.Loader), and specworkflow.FromProfile is now specworkflow.FromWorkflow.

The CLI surface is unchanged: --profile, --profile-dir, and the profiles subcommands keep their names and semantics.

What's New

Canonical Workflow Definitions

Workflow configurations, markdown templates, and structured-evaluation rubrics for every default workflow are embedded in specification-workflow-spec and load as Go structs:

import "github.com/ProductBuildersHQ/specification-workflow-spec/pkg/workflows"

w, err := workflows.DefaultLoader().Load("aws-feature")
// w.Workflow  — config with inheritance resolved (extends enterprise)
// w.Templates — raw markdown per spec type
// w.Rubrics   — *rubric.RubricSet per spec type

Organization overrides chain over the embedded defaults exactly as before; prism-roadmap's canonical canvas assets (OpportunitySpec, BMC) remain the last fallback in the template and rubric chains.

Bridge Helpers

  • templates.NewMapLoader / templates.LoaderForWorkflow — serve a loaded workflow's templates through VisionSpec's templates.Loader interface with the standard fallback chain
  • rubrics.NewMapLoader / rubrics.LoaderForWorkflow — same for rubrics; both sides use structured-evaluation's RubricSet natively
  • types.SpecConfigFromWorkflow — maps a workflow's spec requirements into VisionSpec's SpecConfig for eval, lint, and status

CLI Behavior Refinements

  • The [default] marker in profiles list derives from the embedded workflow set — the four v2mom* workflows are now correctly marked
  • profiles export writes the fully resolved workflow, including methodology and synthesis sections that were previously dropped
  • profiles validate validates against the full workflow schema
  • profiles list and profiles show output is deterministically sorted

Dependency Updates

  • specification-workflow-spec v0.2.0 (new)
  • modelcontextprotocol/go-sdk v1.7.0
  • plexusone/structured-evaluation v0.11.0
  • grokify/prism-roadmap v0.16.1

Upgrade Notes

For Go API consumers:

// Before (v0.14.0)
profile, err := profiles.DefaultLoader().Load("aws-feature")
cfg := cli.ConfigFromProfile(profile)

// After (v0.15.0)
w, err := workflows.DefaultLoader().Load("aws-feature")
cfg := cli.ConfigFromWorkflow(w)

CLI users need no changes.