amal66 lets legal workflows pack up and travel

A fork owner is turning reusable legal know-how into shareable files that move between Mike setups without touching a database.

workflowknowledge-management

amal66 has built a way to export a workflow as a single file and import it somewhere else - a different team, a different Mike instance, a different environment. The idea is that the procedural knowledge baked into a workflow (how your team runs an intake, a review, a drafting pass) stops being locked inside one installation and becomes something you can hand to a colleague or move between staging and production.

The second half of the work is arguably the more durable part: a published, documented format for these packs, with examples and field-by-field explanations, so editors, importers, and other forks all read and validate them the same way. That's the difference between a one-off export button and a format people can actually build on.

So what Worth a look for teams that treat their workflows as a real asset and want to share or version them - though anyone importing packs from outside should treat them as untrusted input.

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 amal66/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`4378b6af`	feat(chapter-31): make workflows exportable and importable	Amal	2026-05-24	↗ GitHub
commit body Chapter: 31 - Workflow portability. Plain-English map: Add endpoints for exporting and importing workflows as `.mikeworkflow.json` files. Why it matters: Workflows capture reusable legal know-how. Users should be able to move them between Mike instances, teams, and environments without database access. Principle: Useful knowledge should be portable. Precedent borrowed: Upstream PR #59. Upstream base: willchen96/mike@d39f580. Original local commit: 212fbbe.
`c32e9307`	docs(chapter-32): define the workflow pack format	Amal	2026-05-24	↗ GitHub
commit body Chapter: 32 - Shared workflow contract. Plain-English map: Add a JSON Schema and human documentation for workflow packs, including examples and field explanations. Why it matters: Portable files need a shared contract. A schema lets editors, importers, and forks validate workflow packs in the same way. Principle: Schema-first formats reduce fragmentation. Precedent borrowed: Upstream PR #34 and workflow-heavy jurisdiction and practice-area forks from the fork report. Upstream base: willchen96/mike@d39f580. Original local commit: 557e647.

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-597.md from inside the repo you want the changes in.

⬇ Download capture-thread-597.md