Skip to content

Release v0.17.0

Release Date: 2026-08-16

This release finishes the roadmap-domain upstream to prism-roadmap that v0.16.0 started, extends the layered rubric taxonomy from the hardened enterprise/AWS-door workflows to every remaining locally-owned rubric, and corrects a modeling error where AWS Working Backwards artifacts were owned by enterprise instead of aws-one-way-door.

Highlights

  • prism-roadmap upstream complete: experience-map and v2mom-summary are now synced from the tagged prism-roadmap v0.18.0 release, converting the last four local stopgaps into prism-synced copies with provenance headers — prism-roadmap is now the single source of truth for all roadmap/discovery/goals content
  • The layered class/blocking/evaluation taxonomy (introduced for enterprise/aws-door rubrics in v0.16.0) now covers all 62 remaining locally-owned rubrics (415 categories), so every consumer can separate advisory Leadership-Principle judgment from blocking implementation-readiness gates
  • AWS Working Backwards artifacts re-homed: press, faq, and the six-pager (narrative-6p) move from enterprise to aws-one-way-door, their actual canonical owner; enterprise becomes the pure contract layer (MRD/PRD/UXD/TRD/TPD/IRD/spec)
  • N/A-with-rationale applicability backported to pbhq-lite's conditional blocking gates, fixing a false-fail the spec-judge calibration surfaced on this initiative's own spec-content library
  • synthesize/init/create/approve now fully respect the project's configured workflow: they previously applied a hardcoded pre-merge Working Backwards ruleset regardless of --profile, so aws-one-way-door's faq wrongly required mrd, and enterprise's bmc couldn't be created, approved, or synthesized at all

Breaking

  • enterprise no longer provides or requires press/faq/narrative-6p. The canonical home is aws-one-way-door (full ownership with AWS Leadership Principle rubrics). aws-two-way-door and the big-tech family still source these artifacts via {from: aws-one-way-door}; non-Working-Backwards methodologies (google, shapeup, jtbd, lean-startup, design-thinking, startup, 0-1) drop the unused optional entries entirely

Added

  • Methodology.Parameters (map[string]any) carries methodology-specific structured config whose shape varies per methodology — Shape Up betting cycles, Continuous Discovery cadence and assumption taxonomy, V2MOM cascading and ProductContext links — previously expressed as top-level profile keys the loader silently dropped
  • "tracking" added to the SpecRequirement.Category enum (used by big-tech's shapeup-scope and discovery-snapshot)
  • not_applicable (N/A-with-rationale) added to pbhq-lite's 6 conditional blocking categories that assume a service/feature: trd api_design/data_models/security_considerations/dependencies and prd user_stories/success_metrics; quick-fix inherits them. Universally-applicable gates (goals, requirements, problem, plan/roadmap execution) intentionally keep no escape hatch
  • experience-map (template + rubric, continuous-discovery) and the v2mom-summary rubric are now prism-synced from prism-roadmap v0.18.0; remaining synced files re-stamped from @v0.17.0 to @v0.18.0
  • class/blocking/evaluation layered taxonomy applied to all 62 remaining locally-owned rubrics across big-tech (+ feature/product/essentials families), google, shapeup, stripe, growth, jtbd, lean-startup, design-thinking, startup, 0-1, pbhq-lite, aws-one-way-door's Working Backwards rubrics, and enterprise's mrd/spec/narrative-1p

Changed

  • rubric_extensions removed and cycles migrated to parameters for the big-tech, big-tech-essentials, and shapeup profiles touched by the AWS artifact re-homing
  • v2mom and continuous-discovery methodology config moved into methodology.parameters; v2mom's dead evaluation block dropped (superseded by the real v2mom-*.rubric.yaml files)

Fixed

  • init now persists the resolved --profile name into visionspec.yaml instead of the unrelated --workflow flag's value (an older mechanism for an external spec-workflows repository) — the chosen embedded-catalog profile was previously forgotten immediately after project creation, so every later command silently fell back to legacy defaults
  • synthesize's required-sources check, prompt guidance, and template resolution now come from the project's actual workflow synthesis rules (profile.yaml's synthesis: block) instead of a hardcoded pre-merge table — fixes aws-one-way-door's faq wrongly requiring mrd, and makes workflow-declared types the legacy table never knew about (e.g. enterprise's bmc) synthesizable for the first time
  • SynthesisInput generalized from six fixed struct fields to map[types.SpecType]string, and prompt building now includes the workflow's own Guidance/PromptContext text — the methodology-specific synthesis instructions every profile.yaml already authors (e.g. aws-two-way-door's exact FAQ question categories) now actually reach the LLM instead of being silently discarded
  • create and approve (CLI and MCP) no longer reject spec types outside types.SpecType's fixed 10-type enum when the project's workflow legitimately defines them (e.g. enterprise's bmc) — create now validates through the workflow's own template loader instead of the closed enum

Documentation

  • tools/prism-sync/README.md rewritten for the post-v0.18.0 world: drop the stale replace-directive / "manual only, cannot run in CI" sections, document syncing from the tagged release, refresh the synced-content table, add an upgrade procedure
  • CLAUDE.md gains a "Synced Content (Generated — Do Not Edit)" section so contributors and agents know not to hand-edit generated catalog files
  • ROADMAP.md: RMI-020 through RMI-029 marked complete with resolution notes; a new Phase 8 files the three follow-ons the review/calibration surfaced (RMI-028 PRD-representation reconciliation, RMI-029 N/A-applicability backport, RMI-030 rebuild visionstudio against merged visionspec)
  • README and MkDocs site aligned with the profile changes above: enterprise no longer lists press/faq in the stage-profile tables, and the profiles show/export sample output is refreshed; the layered class/blocking/evaluation rubric fields (with INV-3 and the not_applicable option) are documented in the custom-profiles guide
  • init/create/synthesize --help no longer hardcode the pre-merge MRD-first flow or a 4-of-25 profile list; they point at visionspec profiles list / visionspec workflow for the real, per-project catalog and sequence

Infrastructure

  • Bump grokify/prism-roadmap to v0.18.0 in both go.mod and tools/prism-sync/go.mod

Compatibility

One breaking change, a relocation:

  • Profiles/callers that assumed enterprise provides press/faq/ narrative-6p need to source them from aws-one-way-door instead (or use a methodology that already does, like aws-two-way-door or big-tech). No known external consumer depended on enterprise for these three spec types specifically.
  • As a consequence of the workflow-awareness fixes above, create/ synthesize now correctly reject spec types a profile doesn't define (e.g. visionspec create narrative-6p under enterprise) instead of silently falling back to the generic embedded default template regardless of profile. Anyone relying on that fallback should switch to a profile that actually owns the type.
  • Everything else is additive.

Installation

go get github.com/ProductBuildersHQ/visionspec@v0.17.0