docs(chapter-32): define the workflow pack format

↗ view on GitHub · Amal · 2026-05-24 · c32e9307

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.
Repository amal66/mike
Author Amal <mamalanand3@gmail.com>
Authored
Parents 4378b6af
Stats 2 files changed , +256
Part of Workflow export/import portability

Capture this commit into my fork

Download a Markdown prompt that tells Claude how to port this exact commit into your working tree. Run it via claude -p < capture-commit-c32e9307.md from inside the repo you want the change in.

⬇ Download capture-commit-c32e9307.md