demand-intake

Collect structured pre-drafting context for demand letters into intake.md.

Updated May 15, 2026
One-click install
npx skills add https://github.com/az9713/claude-for-legal-tutorial --skill demand-intake-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demand-intake
Source: https://github.com/az9713/claude-for-legal-tutorial/tree/main/litigation-legal/skills/demand-intake
Command: npx skills add https://github.com/az9713/claude-for-legal-tutorial --skill demand-intake-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Demand letters often fail because the writer skips structured pre-drafting intake, leading to weak facts, mismatched tone/marking, and missing leverage or privilege guardrails.

Core Features & Use Cases

  • Structured intake capture: Collects demand type, parties, triggering event, legal/contractual basis, desired outcome, deadlines, prior outreach, and distribution details into an intake.md file for downstream drafting.
  • Matter-specific posture first: Forces questions for tone, response window, marking, and signer so the draft aligns to the specific dispute instead of generic defaults.
  • Strategic risk layer (optional/conditional): When the heuristic deems it material or when --full is used, gathers leverage & BATNA, downside tolerance, settlement-communication posture, privilege filters, and admission/accord-and-satisfaction risk to improve draft quality and safety.

Quick Start

Run the demand-intake flow by asking the system to collect intake for a demand letter with the title you provide, then save it for drafting.

Frequently Asked Questions about demand-intake

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

FAQPage Schema
What is pre-drafting intake for a demand letter and why is it necessary?

Demand letter pre-drafting intake is the structured capture of parties, facts, legal basis, and deadlines before drafting. It prevents weak facts, mismatched tone, and missing leverage by creating an intake.md file that guides the downstream draft.

How do I prepare context for drafting a cease-and-desist or breach notice?

To prepare context for a cease-and-desist or breach notice, gather the triggering event, contractual basis, desired outcome, and prior outreach history. This intake process saves the details into a per-matter file to align the draft to the specific dispute.

Does the intake process capture BATNA and settlement communication posture?

The intake process captures BATNA, leverage, downside tolerance, and settlement-communication posture when the dispute is deemed material or when using the full mode. This strategic risk layer improves draft quality and safety.

Can I use this intake workflow for employment separation and preservation demands?

Yes, you can use this intake workflow for employment separation, preservation demands, payment demands, and cease-and-desist letters. It collects matter-specific posture, response windows, and distribution details for each dispute type.

What privilege filters and admission risks are collected during legal intake?

During legal intake, privilege filters and admission or accord-and-satisfaction risks are collected to establish a settlement-communication protection posture. This guards the downstream demand draft against unintended waivers or damaging admissions.

How do I save intake context for a downstream demand-letter drafting step?

To save intake context, the system writes a per-matter intake.md file under the demand-letters slug path. This file stores the structured context, strategic leverage, and privilege posture required for the subsequent drafting workflow.