Release v0.18.0¶
Release Date: 2026-09-26
This release adds a second distribution path for VisionSpec's methodology
catalog: alongside the existing visionspec init/CLI/MCP authoring flow, a
workflow family can now be exported as native
GitHub Spec Kit extensions, workflows,
and bundles, for use in any Spec Kit project — VisionSpec-authored or not.
Highlights¶
visionspec speckit export: packages a workflow family as Spec Kit extensions. The first family shipped,aws-one-way-door, splits by spec category into aone-way-doorproduct extension (press, faq, mrd, prd, narrative-6p, uxd) and aone-way-door-engineeringadd-on (trd, tpd, ird). Each spec type becomes a Spec Kit command that authors its document from the family's template and self-evaluates against the family's rubric before reporting donerisk-adjustedtriage workflow: a hand-authored front door that routes any piece of work by reversibility — a bug goes to Spec Kit's built-in bug pipeline, a reversible two-way-door feature goes to the corespecify/plan/tasks/implementflow, and a hard-to-reverse initiative gets the full one-way-door chain with its review gates. A generatedone-way-door-chainworkflow, compiled straight from the family's execution sequence and review gates, covers the case where the ceremony decision is already made- Role bundles and catalogs:
product-management(the product extension +risk-adjusted) andproduct-builders(adds the engineering extension) let a team install the whole methodology with one command, with catalog JSON files for eventual community-catalog discovery - Spec type ids are now a documented, stable contract:
Execution.Sequenceentries were already the loader-derived template-filename stem; this makes that node-identity contract explicit and adds a matchingReviewGate.StepID(), so the exporter (and any future consumer) has a stable identifier to rely on instead of reinventing one - RMI-030 complete: the spec judge now sees the layered class/blocking/evaluation rubric taxonomy introduced in v0.16.0/v0.17.0
Added¶
pkg/speckit: the exporter package —BuildExtensionssplits a family's execution sequence by spec category into product/engineering extensions;BuildWorkflowcompiles a family's full sequence and review gates into a single workflow.ymlvisionspec speckit export [workflow] [-o dir] [--check]CLI command;--checkverifies committed artifacts still match the generator instead of writing, for CIspeckit/: the generatedone-way-doorandone-way-door-engineeringextensions andone-way-door-chainworkflow, the hand-authoredrisk-adjustedworkflow, theproduct-management/product-buildersbundles, and their component catalogs — every generated file carries aCode generated ...; DO NOT EDITprovenance header, enforced by--checkand a repo-level drift testReviewGate.ID/StepID()onpkg/workflow.ReviewGate, defaulting to a kebab-casedActionwhen no explicit id is set
Documentation¶
- New Spec Kit Plugins guide: installing
the exported extensions and workflows into a real external Spec Kit
project and working a real initiative through them, conversationally as
the primary path with
specify workflow runas the unattended/CI alternative speckit/README.md: component reference, install instructions, and the release/catalog story- Every methodology framework page (AWS, Google, Stripe, Big Tech, Shape Up, Continuous Discovery, Lean Startup, Design Thinking, JTBD, OpportunitySpec) now explicitly discloses it is ProductBuildersHQ's independent interpretation, not official material from the named company or practitioner
- RMI-030 marked complete in
ROADMAP.md
Infrastructure¶
- Tag-triggered
release-speckit.yamlGitHub Actions workflow: verifies the generator drift gate, zips each extension and bundle with its manifest at the zip root, checksums everything, and publishes a GitHub release
Compatibility¶
Fully additive — no breaking changes. pkg/workflow.ReviewGate.ID is a new
omitempty field; existing profiles and exported output are unaffected.
Installation¶
go get github.com/ProductBuildersHQ/[email protected]