open-legal-products moves Mike's workflow catalog to YAML

Mike's built-in legal workflows now follow the same manifest convention as the workflow library they draw from.

workflowinfrastructure

The project has updated how it finds the workflow packs used to build its system workflows. The change replaces the older JSON-based signposts with YAML, keeping Mike aligned with the workflow repository's new packaging format.

This is a small but useful piece of maintenance: the workflow build was successfully rebuilt under the new convention, producing all 24 system workflows. For users, the immediate experience should stay familiar. The value is in reducing friction as the workflow library evolves, so new or updated legal workflows can be recognised consistently rather than falling through a mismatch between repositories.

So what Legal teams and product builders relying on Mike's reusable workflows should care because the underlying workflow catalogue is being kept dependable as it changes.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from open-legal-products/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
5bf224f7 Discover workflow packs from YAML manifests willchen96 2026-07-28 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1332.md from inside the repo you want the changes in.

⬇ Download capture-thread-1332.md