Usage guide reveals AmCollective's workflow deployment and PE use cases
adamwolfe2 adds a 178-line GUIDE.md written for AM Collective's internal legal team. The document is too branded to import directly, but it names specific workflows they are running in production and how they pitch them to a PE/credit audience.
The guide describes six use cases: ad-hoc contract review, a 21-point Credit Agreement Summary workflow, a 15-area Shareholder Agreement Summary workflow, a CP Checklist workflow that produces a formatted landscape Word table, tabular multi-document comparison, and chat with citations. It points to legal.amcollectivecapital.com and states the model is Claude Opus 4.7.
The Credit Agreement Summary section is the most detailed: 21 extraction points covering parties, facilities, interest rate mechanics (SOFR/EURIBOR/margin/ratchet), repayment schedule, financial covenants with testing frequency and cure rights, security classes, Events of Default with grace periods and cross-default, change of control triggers, prepayment fees and soft-call protections, and governing law. The guide frames the output as replacing a junior associate's "$400-800 first read."
The CP Checklist workflow is worth noting separately -- it produces a table organized by category (Corporate, Financial, Legal, Security) with columns for clause number, plain-English description, and a blank status column. That output shape suggests a specific workflow definition exists somewhere in the fork.
This document cannot be adopted as-is; the URL, branding, and model name are hardcoded for AmCollective. Its value is as a signal: these are the workflows adamwolfe2's team considers production-ready and worth explaining to business users. If those workflow definitions exist in the fork's codebase, they are worth examining.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?