memoforge
From one legal question to a finished .docx memo.
Cowork plugin that mirrors a small legal team. Fifteen specialists run intake, parallel statutory + case-law + doctrinal research, currency check, IRAC drafting, five-reviewer peer review, mediation, up to three revision rounds, and client-readiness polish — then ship memo.docx with the full source pack and a per-reviewer audit trail. You ask. The plugin works. You read.
From a research-grade question to a court-citable memo.
A four-stage flow runs underneath: intake gathers facts and scope; three researchers go out in parallel; the writer drafts IRAC; five reviewers stress-test the draft, a mediator consolidates findings, the writer revises up to three rounds, and a client-readiness polish ships memo.docx. Nine phases, four mandatory human checkpoints.
.docx plus full audit trail.
Why naive memo prompts produce unusable memos.
Hallucinated citations. One model writing one draft will invent statutes and misquote cases. The model that wrote the citation has no incentive to verify it, so nothing catches the error before it reaches your inbox.
No contrary authority. The same model that drafted the analysis will not stress-test it. You get a confident one-sided read — and no idea where opposing counsel would attack first.
No currency check. A 2022 judgment that was overruled in 2024 will still show up as authority. A regulation cross-referencing a repealed act will still get cited. Nothing flags it.
memoforge runs specialists that disagree with each other before the memo ever reaches you.
A statutory researcher pulls primary acts. A citation auditor checks that every claim traces to a source. A currency checker verifies cited judgments still represent current law. A counter-argument reviewer drafts the opposing read. A mediator consolidates the disagreements into one revision list, and a client-readiness reviewer makes the final call.
The output isn't generic disclaimers — it's a memo with named contrary authority, concrete risk scores, and recommendations a partner can actually sign off on.
Brief or Full — pick the depth at the second checkpoint.
Both modes run the same orchestrator and the same gates. Brief stays narrow: statutory research only, three reviewers, one revision, no final polish. Full goes wide: statutes + case law + doctrine, all five reviewers, up to three revisions, and a client-readiness pass at the end.
- Length
- 2–3 pages
- Research
- statutory only
- Reviewers
- 3 of 5
- Revisions
- 1 round
- Polish
- no
Use for a low-stakes question — a deal term that just landed, a vendor's privacy claim, a fast read for an internal Slack thread.
- Length
- 5–8 pages
- Research
- statutes + case law + doctrine
- Reviewers
- all 5
- Revisions
- up to 3 rounds
- Polish
- client-readiness pass
- Runtime
- ~60–90 min wall-clock
Use when the memo is going outside the legal team — pre-launch sign-off, regulatory response, board paper, contested or novel issue where a counter-argument review matters.
Fifteen specialists, one orchestrator.
Each agent does one thing — and challenges the next one's output. A statutory researcher doesn't review style. A clarity reviewer doesn't check citations. Disagreement is the design, not a bug.
Not just a memo — the whole audit trail.
Every memo ships with the source pack it was built on, every draft revision, a per-reviewer record of what was flagged and how it was resolved, and an honest verdict. If a partner asks "where did this citation come from?", the answer is one folder away.
memo.docx is grounded in something inside research/. The citation auditor enforces it — if a sentence in the draft doesn't trace to a source in the pack, it gets flagged in reviews/ and revised before export. And the verdict is honest: approved, forced_exit_on_v3 (revision budget reached with unresolved issues), or manual_review_required. No false confidence.
Make every memo sound like your firm wrote it.
By default the writer follows a built-in house style — concise, no em-dashes, OSCOLA-flavoured citations. Style Studio turns a folder of your own example memos (or a written style guide) into a saved profile that all reviewers defer to. Substantive checks — citation accuracy, IRAC structure, contrary authority — stay uniform.
~/.claude/plugin-data/memoforge/profiles/<name>/. Open and tweak by hand any time.
Install in Cowork. Connect two databases. Ask.
memoforge bundles two MCP servers: Legal Data Hunter for multi-jurisdictional law and CourtListener for US case law. Connect them once from the plugin panel — the first call may trigger an OAuth sign-in. If you skip this step, the pipeline still runs against official portals via WebFetch, and the final memo carries a banner asking you to verify each citation by hand.
memoforge-1.1.1.zip from Releases. The plugin auto-registers its two bundled MCP servers via .mcp.json.
/memoforge:memo with your legal question. memoforge handles multi-part questions in a single memo — each part becomes its own analysed issue with separate citations.
The orchestrator pauses four times for your input. Everything between pauses runs autonomously with a live dashboard in the sidebar.
- Intake
- Up to 10 questions about facts the triage analyst flagged as missing. Type
proceedto accept conservative defaults. - answer: <facts>
- Mode
- Pick Brief or Full. Once per task.
- mode: brief
- Plan
- Approve, edit, or cancel the proposed research plan — jurisdictions, issues, source types.
- approve
- Source review
- After research and source-pack assembly, inspect what was found before drafting begins.
- continue
What memoforge won't do — and where your data goes.
memoforge is built around domains it handles well: EU data protection (GDPR, AI Act, NIS2, DSA), US privacy (CCPA, HIPAA, sectoral), UK consumer law, cross-border compliance. The pipeline classifies the query and picks researchers accordingly — it does not assume a specific jurisdiction. The honest caveats are below.
Not a substitute for a lawyer. The memo is a research-grade draft. A qualified lawyer must review before any client use, especially for regulated advice. The verdict at the end of the run (approved, forced_exit_on_v3, manual_review_required) is a signal, not a sign-off.
English on the output. You can ask in other languages but the memo is written in English.
No client interview. The intake step asks about facts you already know; it does not ask follow-up questions about the underlying business.
Currency is best-effort. The currency check verifies cross-references and the status of cited judgments against the connected databases. For litigation-sensitive citations, verify each judgment is still good law before relying on the memo.
Everything memoforge writes lives on your machine, inside the output folder you chose. Default is ~/Documents/memoforge/; override via $CLAUDE_PLUGIN_OPTION_OUTPUT_FOLDER or $MEMOFORGE_OUTPUT_FOLDER. No shared backend, no server, no telemetry.
MCP calls reach Legal Data Hunter, CourtListener, and any official portals you allow via WebFetch using your credentials, authenticated in Cowork. The plugin never proxies or stores those credentials itself. The audit trail (events.jsonl, draft versions, reviewer outputs) stays in the task folder until you delete it.