Legal Demand Letter Response Draft

Map allegations to contract language and draft a response letter with no unintended admissions.

Legal Demand Letter Response Draft

Purpose

Map allegations to contract language and draft a response letter with no unintended admissions.

Routing

Use when: Use when a demand letter must be analyzed and answered against contract language.
Do not use when: Do not use when the task is generic writing unrelated to legal allegations.
Outputs: Allegation map and response draft with section-level legal grounding.
Success criteria: Produces a defensible response draft, avoids unsupported admissions, and writes both artifacts.

Trigger Examples

Positive

Use the legal-demand-letter-response-draft skill for this request.
Help me with legal demand letter response draft.
Use when a demand letter must be analyzed and answered against contract language.
Legal Demand Letter Response Draft: provide an actionable result.

Negative

Do not use when the task is generic writing unrelated to legal allegations.
Do not use legal-demand-letter-response-draft for unrelated requests.
This request is outside legal demand letter response draft scope.
This is conceptual discussion only; no tool workflow is needed.

Parameters

Name	Type	Required	Description
agreement_path	string	No	Optional explicit path to the governing contract
demand_letter_path	string	No	Optional explicit path to the demand letter
facts_path	string	No	Optional chronology/facts memo path
client_role	select	No	Role of your client in the dispute
response_output_path	string	No	Where to write the draft response letter
issues_table_output_path	string	No	Where to write the allegation mapping table

Runtime Prompt

Current runtime prompt length: 1932 characters.
Runtime prompt is defined directly in ../legal-demand-letter-response-draft.json.

Added: September 23, 2026 · Last updated: October 13, 2026

View on GitHub Download

Files (1)

SKILL.mdSKILL.md

Jurisdiction: General
Practice area: Contracts
License: MIT
Author: CoWork-OS
Source: general/contracts/skills/legal-demand-letter-response-draft

Test Legal Demand Letter Response Draft

Ask a legal question — get an answer generated live from this skill’s instructions.

Sign in to test this skill.

$ai-governance-legal:vendor-ai-review

Apache-2.0GeneralContracts

Review vendor AI terms — agreement, addendum, or ToS AI provisions — against your governance positions; flag training-on-data, liability, model changes, and AI policy consistency. Use when user says "review this AI agreement", "check OpenAI terms", "what did we agree to with [vendor]", "vendor sent an AI addendum", "is this AI contract okay", or attaches vendor AI terms.

$commercial-legal:amendment-history

Apache-2.0GeneralContracts

Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.

$commercial-legal:review

Apache-2.0GeneralContracts

Review a vendor agreement, NDA, or SaaS subscription against your playbook. Identifies the agreement structure from titles, routes to the right review skill (vendor-agreement-review, nda-review, saas-msa-review), and integrates the output into a single memo. Use when the user says "review this contract", "check this MSA", "is this NDA okay", "look at this SaaS agreement", or attaches an inbound agreement for review.

Amendment history

Apache-2.0GeneralContracts

追溯合同从基础协议到所有修订的变更轨迹——可以是所有变更的时间线摘要，也可以是特定条款的追踪。当用户说"这个合同历次改了什么""显示修订历史" "最新的[条款]在哪里""[条款]如何演变的"或上传多个版本的协议时使用。

Amendment history

Apache-2.0GeneralContracts

Trace how a contract has changed across its base agreement and all amendments, ek protokoller, zeyilnameler, and related variation documents. Produces either a chronological summary of all changes or a provision trace for a specific clause while preserving the original skill function.

Amendment history

Apache-2.0GeneralContracts

Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.