demand-draft

Draft review-ready demand letters from completed litigation intakes.

109|20|Updated Mar 7, 2025
One-click install
npx skills add https://github.com/stakwork/stakgraph --skill demand-draft-stakwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demand-draft
Source: https://github.com/stakwork/stakgraph/tree/main/mcp/skills/litigation-legal/demand-draft
Command: npx skills add https://github.com/stakwork/stakgraph --skill demand-draft-stakwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a completed legal demand intake into a structured, review-ready demand letter while reducing the risk of privilege waivers, admissions, unsupported factual assertions, and improper settlement-communication treatment.

Core Features & Use Cases

  • Pre-Draft Risk Gate: Reviews privilege, admission, accord-and-satisfaction, FRE 408 or state-equivalent posture, waiver, tone, and factual-accuracy issues before drafting.
  • Structured Letter Drafting: Produces demand letters for payment disputes, breaches, cease-and-desist matters, employment separations, and preservation requests using verified facts and citation placeholders.
  • Document and Matter Workflow: Creates a versioned DOCX draft, an internal post-send checklist, and a materiality-based offer to create a tracked matter.
  • Use Case: Give the Skill a completed intake for an unpaid invoice or contract breach, confirm the required review gates, and receive an attorney-review draft with verification flags, preservation language, deadlines, and follow-up tracking.

Quick Start

Use the demand-draft skill with a completed intake slug to run the pre-draft gate and prepare a review-ready demand letter.

Frequently Asked Questions about demand-draft

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft a demand letter without waiving privilege or making admissions?

To draft a demand letter without waiving privilege, use a pre-draft risk gate that reviews posture, admissions, and settlement-communication treatment before generating the document. This process flags FRE 408 implications and factual accuracy issues, producing a review-ready draft with verification markers.

What is the process for generating a breach or cease-and-desist letter from an intake?

Generating a breach or cease-and-desist letter requires a completed litigation intake, jurisdiction review, and source-traceable facts. The process applies a pre-draft risk gate, structures verified facts with citation placeholders, and outputs a versioned DOCX file with a post-send checklist.

Can I create a preservation demand for employment separation disputes using this workflow?

Yes, you can create a preservation demand for employment separation disputes by processing a completed intake through the structured drafting workflow. The output includes preservation language, deadlines, citation placeholders, and an internal post-send checklist to track the matter.

Do I need a completed legal intake to generate a demand letter?

Yes, a completed legal intake is required to generate a demand letter. The drafting process depends on source-traceable facts, jurisdiction information, and posture review from the intake to run the pre-draft risk gate and produce accurate citation placeholders.

What is the best way to handle FRE 408 settlement-communication risks in demand letters?

The best way to handle FRE 408 settlement-communication risks is applying a pre-draft risk gate that evaluates posture and tone before drafting. This prevents improper settlement-communication treatment and ensures the final document contains appropriate preservation language and verification flags.

What are the limitations of automated legal drafting for litigation demand letters?

Automated legal drafting for litigation demand letters requires a completed intake and cannot verify facts independently; it outputs citation placeholders and verification flags for attorney review. It produces a review-ready DOCX draft rather than a final send-ready document, necessitating manual privilege and accuracy checks.