Eight U.S. legal task presets added to the built-in workflow catalog

`fb699b29` replaces Gary's upstream workflow definitions with eight U.S.-focused Saved Legal Tasks, adds an onboarding checklist component, and updates the terminology map to surface "Saved Legal Tasks" as the user-facing label. The task prompts are the importable artifact - they're in `builtinWorkflows.ts` on both the frontend and backend, decoupled from Gary's branding.

workflowdrafting

The eight tasks are: Contract Review, Litigation Memo, Case Chronology, Discovery Summary, Deposition Prep, Demand Letter Draft, Client Intake Summary, and Privilege Review. Each is defined by a string id, a display title, and a prompt_md block. The prompts share a consistent structure: a brief framing statement, a set of explicit instructions (use only provided materials, do not invent statutes or case law, label assumptions, use U.S. legal terminology), and a numbered output section list. For example, Contract Review requests six output sections: Executive Summary, Key Terms, Potential Risks, Missing or Ambiguous Provisions, Negotiation Points, and an Attorney Follow-Up Checklist.

The definitions live in backend/src/lib/builtinWorkflows.ts (backend) and frontend/src/app/components/workflows/builtinWorkflows.ts (frontend), with a 74-line test file. The test file exercises the task list to confirm the expected IDs and titles are present - the eight task IDs become the recognized set for downstream features like the Review Table's Suggested Saved Legal Task column.

The onboarding checklist in OnboardingChecklist.tsx (143 lines) is threaded into the initial view, the project page, and the projects overview. It surfaces "Start Your First Matter" prompts for new users. This component is Gary-specific UX and tightly coupled to the fork's product framing.

The "Workflows" → "Saved Legal Tasks" rename is tracked in the terminology map. User-facing labels, sidebar text, and empty-state copy all use the new name consistently after this commit.

So what The prompt definitions in `builtinWorkflows.ts` are worth reading if you're building a U.S. legal AI product. They encode a practical approach to grounding legal AI outputs - explicit "do not invent authorities" constraints, structured output sections, attorney-review framing throughout. The prompts are independent of Gary's stack and could be adapted for any RAG or chat product. The onboarding component and the terminology changes are fork-specific and not worth porting. The task IDs matter if you plan to use the Review Table's Suggested Saved Legal Task feature - downstream code matches against those exact strings.

View this fork on GitHub →

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

Commits in this thread

1 commit from zgbrenner/gary, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
fb699b29 feat: expand built-in Saved Legal Tasks and standardize U.S. terminology Zack Brenner 2026-05-19 ↗ GitHub

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

⬇ Download capture-thread-530.md