⚖MikeWatch Forks of the Mike legal-AI codebase, distilled for legal-tech readers
Home · amiel-35/mikelaw-oss · this thread

amiel-35 wants Mike's workflows to travel

A proposed standard format that would let legal review templates be written once, versioned, translated, and shared between forks.

workflowi18n

This is a proposal, not shipped code - deliberately so. amiel-35 has sketched a common format for describing Mike's workflows so they could be authored once and then versioned, localized, and swapped between forks like any other shared document, without touching the running app yet.

The format covers two kinds of work: a free-form assistant task, such as summarising a document, and a structured review that fills out a table. The worked example is an NDA review with columns for the parties, the confidentiality obligations, term and survival, and a risk rating. The proposed folder layout sorts these packs by language, jurisdiction, and practice area - leaving room for region-specific versions later on.

So what Anyone maintaining a library of legal-review templates should watch this: it's the early scaffolding for sharing and localising them, rather than rebuilding the same workflows inside every fork.

View this fork on GitHub →

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

Commits in this thread

2 commits from amiel-35/mikelaw-oss, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
f36519a0 docs(workflows): add declarative workflow pack format Amiel Lavon 2026-05-05 ↗ GitHub
557a990c docs(workflows): add declarative workflow pack format Amiel Lavon 2026-05-05 ↗ 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-307.md from inside the repo you want the changes in.

⬇ Download capture-thread-307.md