# Ecvc Draft Markup Ira > Marking up an investors’ rights agreement from the Company’s perspective requires comparing the counterparty draft against the negotiated term sheet, identifying added investor-favorable language, and reviewing provisions that can create spillover effects among registration, information, pro rata, drag-along, and most-favored-nation mechanics. - Skill: `finchipaiorg/ecvc-draft-markup-ira` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/ecvc-draft-markup-ira` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/ecvc-draft-markup-ira/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/ecvc-draft-markup-ira --- # Skill: Draft Markup of Investors’ Rights Agreement ## 1. Subject-matter triage - Treat the prior IRA, term sheet, playbook, cap table, and client email as a single source set; reconcile them before drafting. - Confirm whether the draft is a clean market form or a revised form with embedded investor-favorable edits, then mark only the deltas that matter from the Company’s perspective. - If multiple financings, classes, investors, or side arrangements are referenced, enumerate the affected parties and provisions first, then analyze each one separately. ## 2. Failure modes the skill is correcting - The markup restores provisions from the prior agreement but misses new investor-favorable additions in the counterparty draft that were not bargained for in the term sheet. - The memo identifies issues without tying them to the operative source documents or to the specific business consequence for the Company. - Cross-effects among registration, information, pro rata, drag-along, and most-favored-nation mechanics are treated as isolated edits when they can compound. - The redline relies only on formatting and does not remain legible as a textual markup after export. - The commentary flags concerns but does not close each point with a concrete Company-side ask. ## 3. Legal frameworks / domain conventions that apply - Use the negotiated term sheet as the primary benchmark; where the draft deviates, test whether the added language is market, overreaching, or inconsistent with the agreed package. - Registration rights: check demand rights, initiation threshold, deferral period, cutback order, underwriting mechanics, and expense allocation under the registration-rights framework reflected in the source documents. - Information rights: confirm the Major Investor threshold, reporting cadence, and any competitor-based carveout; narrow any termination trigger that is overbroad or subjective. - Pro rata rights: verify the allocation formula, participation mechanics, and whether multiple investor tiers create unintended stacking or dilution effects. - Drag-along mechanics: confirm consent threshold, sale mechanics, and whether the draft preserves an express floor or other protection against a forced nominal or distressed sale. - Most-favored-nation language: test whether the clause is one-time, election-based, and bounded to a defined comparison universe rather than an automatic ratchet across later amendments or side rights. - Company-side drafting should preserve consistency with the cap table, the financing economics, and any client email instructions that narrow or expand the agreed position. ## 4. Analytical scaffolds - Build a term-sheet checklist before redlining: for each deal point, record whether the draft matches, expands, narrows, or omits the agreed position. - For each substantive change, identify: what the draft says, what the agreed package says, why the deviation matters to the Company, and the exact replacement language to propose. - For every issue in the commentary memo, include a severity label from a fixed ordinal scale stated at the top, and apply the same scale uniformly. - For every issue, close the analysis by tying the point to a source-document threshold or other objective deal parameter, identifying the interacting clause or document, and stating the downstream Company consequence. - Where a provision can affect more than one investor, tranche, or closing scenario, analyze each separately rather than using a representative pass. - When a legal proposition is asserted, anchor it to the governing contractual framework or the cited market convention in the source set; do not state conclusions in purely descriptive terms. - Draft the Company’s position as a specific counterproposal, not a general objection. - In the markup, make each substantive edit legible in plain text as well as visually. ## 5. Vertical / structural / temporal relationships - Check whether amendments, waivers, side letters, or later closings would expand the draft’s rights beyond the intended investor class. - Test whether later-favored terms can flow backward through MFN language or forward into future financings. - Check whether registration, information, and pro rata rights operate only during the intended investment horizon or continue after dilution, transfer, or conversion events. - Confirm whether any thresholds are measured at signing, closing, or post-closing capitalization, and keep the timing consistent across the document set. ## 6. Output structure conventions - Produce the marked-up IRA as the primary deliverable first, then the commentary memo after the markup exists and is complete. - Use a robust textual redline convention in the document itself so changes are readable outside Word styling: [DELETED: …], [INSERTED: …], and [REPLACED: old → new], with a short [Rationale: …] on each substantive change. - The markup should preserve the underlying agreement structure while exposing every Company-side edit clearly. - The commentary memo should be organized by issue, with each entry including: - Severity - Draft position - Benchmark from the prior IRA / term sheet / playbook / client email - Deviation and Company impact - Proposed counterlanguage or negotiating ask - Include a concluding Recommended Actions section that assigns each action to the relevant role and ties it to the closing or revision milestone in the source documents. - Keep the deliverables conventional in shape; do not mirror any hidden checklist or use rubric-specific labels. - Before finishing, confirm that both deliverables are complete, non-empty, and contain operative markup and commentary rather than a description of them.