demand-draft

Run the demand-draft workflow with the intake slug, for example /demand-draft [slug]. It loads the intake file, runs the pre-draft gate checklist, drafts in chat for your review, then writes a versioned .docx and a post-send checklist.

The pre-draft gate is a seven-item checklist covering privilege filter, admission risk, accord-and-satisfaction, settlement-communication posture under FRE 408 or state equivalents, waiver scan, tone, and factual accuracy. Drafting does not proceed until each item is engaged.

Yes, the --skip-gate flag bypasses the pre-draft checklist, but the skip is logged and noted in the draft file. It is intended only for cases where the checklist was already run separately and documented.

No. The draft uses [CITE:___] placeholders and never invents citations. Authorities supplied in the intake are used faithfully, and every citation must be verified through a citator such as Westlaw or CourtListener before sending.

Soft templates cover payment demands, breach and cure notices, cease-and-desist letters, employment separation demands, and preservation demands. If a seed document exists in the practice configuration, its structure and tone take priority over the soft templates.

Use demand-received when you are responding to an inbound demand letter, which is common for in-house defense practitioners. Demand-draft is for asserting claims outbound, typically from a plaintiff or claimant posture.