| name | redline-emailer |
| title | Input Modes |
| description | Translates contract redlines into client-ready or opposing-counsel emails. Accepts three input modes: (1) a .docx with tracked changes, (2) a redlined PDF with strikethrough/underline formatting, or (3) a verbal description of changes. Produces a copy-paste-ready email, tone-matched to the recipient: plain-English for own clients, professional legal cover for opposing counsel. Use when the attorney says "write the redline email", "summarize these changes for the client", "draft a cover email for the redline", "explain these edits to opposing counsel", or "turn this redline into an email". Do NOT use for drafting contracts or generating redlines — use the relevant drafter skill. Do NOT use for diffing two clean (non-redlined) document versions. |
| author | bstevescherer |
| author_url | https://github.com/bstevescherer/heycounsel-community/tree/main/skills/redline-emailer |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | contracts |
| language | en |
Input Modes
| Mode | Trigger | Input |
|---|
| A: .docx Tracked Changes | User provides a .docx with Track Changes | Parse Word XML for w:del/w:ins elements |
| B: Redlined PDF | User provides a .pdf with redline formatting | Parse PDF for strikethrough/underline/color-coded text |
| C: Verbal Description | User describes changes, no file | Work from the attorney's description |
Auto-detect the mode from what the user provides. See references/intake-questions.md Q1.
Instructions
Step 1: Load References
Read before doing anything:
references/intake-questions.md — short intake flow (4 questions, most auto-detectable)references/email-templates.md — tone guides and structural templates for both recipient typesreferences/validation-rules.md — quality checks per recipient type
Step 2: Run Intake
Follow references/intake-questions.md. This should take 60 seconds or less.
What you must know before proceeding:
- Input mode (auto-detect from file type)
- Recipient: client or opposing counsel
- Contract identity: title, parties
- Special instructions (if any)
Do NOT re-ask questions the attorney already answered in their initial request.
If the attorney says "write the redline email for opposing counsel" and drops a
.docx, you have all four answers — go straight to Step 3.
Step 3: Extract Changes
This step varies by input mode.
Mode A: .docx with Tracked Changes
Extract changes from Word XML. The .docx format uses the same elements that
redline_engine.py writes — we're reading them instead.
Namespace:
W = 'http://schemas.openxmlformats.org/wordprocessingml/2006/main'
Element patterns:
<w:del> → <w:r> → <w:delText> = deleted text<w:ins> → <w:r> → = inserted text
