Five EU/UK in-house workflows added alongside Mike's original three finance workflows

counselos adds five built-in workflows targeting EU/UK in-house counsel - NDA playbook review, GDPR Article 28 DPA review, EU AI Act vendor addendum review, MSA/order-form red-flag memo, and vendor intake triage - and after an initial "replace" commit, reverses course and restores the three upstream finance workflows as well. The result is eight total built-ins.

contract-reviewcompliance

The first commit replaces Mike's builtin-cp-checklist, builtin-credit-summary, and builtin-sha-summary with five new ones. The second commit (ddbf7367) restores the originals verbatim and updates the README from "rebuilt" to "extended." The commit message is explicit: keep the workflows useful for in-house lawyers who touch credit/SHA work, and keep upstream merges clean by not removing existing IDs.

The five new prompts are long and structurally opinionated. Each pre-declares a fixed section layout and a classification scheme. The NDA review uses RED/AMBER/GREEN with a deviation table and a sign-off recommendation paragraph. The DPA review outputs an eight-row Article 28(3) compliance matrix, a transfer-mechanism table, and ACCEPT/NEGOTIATE/REJECT. The AI Act addendum review covers Article 50 transparency, GPAI obligations under Articles 53-55, and customer-facing risk allocation. The MSA review produces a traffic-light memo intended for a non-lawyer business owner. Vendor intake triage assigns a risk tier and maps to GDPR/AI Act/DORA/NIS2 with required approvers and legal turnaround SLAs.

Every prompt includes a self-check instruction - the DPA prompt, for example, tells the model to verify that the transfer-mechanism table is consistent with the sub-processor list before finalizing. The DPA prompt is the most coupled to the generate_docx API: it specifies exact section headings, table column names, and an eight-row structure. If your fork's generate_docx schema has diverged from upstream, that prompt needs adjustment before it'll produce valid output.

The frontend re-add of the upstream workflows adds a practice field ("General Transactions" / "Finance" / "Corporate") that the original entries didn't carry. Minor schema delta, but worth noting if your frontend's workflow list component reads that field.

So what Worth a look if you serve EU/UK in-house counsel and want production-quality prompt templates rather than writing them from scratch. Pull the post-`ddbf7367` additive form - it leaves upstream's workflow IDs intact. The prompt content (structured sections + classification + self-check) is a useful pattern regardless of the EU framing. Check the `generate_docx` section/table API shape in your fork before adopting the DPA workflow wholesale.

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

Commits in this thread

2 commits from counselos/mike-inhouse, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`5193ef54`	feat: replace finance assistant workflows with in-house EU workflows	counselos	2026-05-04	↗ GitHub
`ddbf7367`	feat: keep Mike's three finance workflows alongside the five in-house ones	counselos	2026-05-05	↗ GitHub
commit body Restores builtin-cp-checklist, builtin-credit-summary, and builtin-sha-summary in both backend and frontend builtin workflow lists. The fork is additive rather than a replacement, which keeps the workflows useful for in-house lawyers who occasionally do touch credit agreements or shareholder agreements, and makes upstream merges cleaner.

SHA

Subject

Author

Date

5193ef54

feat: replace finance assistant workflows with in-house EU workflows

counselos

2026-05-04

↗ GitHub

ddbf7367

feat: keep Mike's three finance workflows alongside the five in-house ones

counselos

2026-05-05

↗ GitHub

commit body

Restores builtin-cp-checklist, builtin-credit-summary, and builtin-sha-summary
in both backend and frontend builtin workflow lists. The fork is additive
rather than a replacement, which keeps the workflows useful for in-house
lawyers who occasionally do touch credit agreements or shareholder agreements,
and makes upstream merges cleaner.

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