# Ecvc Draft Rofr Waiver > A right-of-first-refusal waiver for a secondary stock sale should be narrowly scoped to the specific transfer, address vesting and any repurchase-right status, identify the applicable securities-law transfer pathway in general terms, include legend-removal procedures, and require the transferee to execute a joinder to the applicable transfer-restriction agreement. - Skill: `finchipaiorg/ecvc-draft-rofr-waiver` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/ecvc-draft-rofr-waiver` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/ecvc-draft-rofr-waiver/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-rofr-waiver --- # Skill: Draft Right-of-First-Refusal Waiver ## 1. Subject-matter triage - Treat this as a two-part task: an issues memo plus a standalone waiver/consent letter. - Read the source package first for the transfer parties, share class, share count, consideration, vesting status, repurchase-right status, transfer-restriction regime, and any transfer-agent mechanics. - If multiple holders, tranches, or transfer paths appear, separate them before drafting; do not blend distinct transfers into one generic consent. - Draft the waiver for the specific proposed transfer only; do not create a standing waiver for future dispositions. ## 2. Failure modes the skill is correcting - The waiver is broader than the identified sale and unintentionally weakens transfer restrictions for later transfers. - The transfer is consented to without addressing whether the shares are fully vested or whether any repurchase right still attaches. - The transferee is not required to remain bound by the existing transfer-restriction and co-sale framework. - The securities-law mechanics are left vague, making the transfer difficult to process at closing. - Legend removal and transfer-agent instructions are omitted, leaving the mechanics unresolved. - The issues memo describes problems without ranking them or tying each to a concrete consequence and next step. ## 3. Legal frameworks / domain conventions that apply - Use the governing transfer-restriction agreement, charter-based transfer limits, investor consent rights, and any related co-sale or participation mechanics as the baseline contractual framework. - Address vested versus unvested equity separately; if unvested shares are included, the waiver must not imply that repurchase rights are waived unless the source documents support that result. - Identify the relevant private-company secondary-transfer pathway in general terms under the Securities Act of 1933 and applicable state-law transfer mechanics, rather than overstating a definitive exemption without support. - Where a transfer-agent or issuer instruction is needed, the waiver should state the process for legend removal and for issuance of any replacement book-entry or certificate evidence. - The transferee should execute a joinder or counterpart agreement so the existing transfer restrictions continue to apply to the transferred shares after closing. - Any consent should be expressly limited to the described transfer, with no implied consent for future sales, pledges, gifts, or other dispositions. - For the memo, cite controlling authority by name and section when relying on a legal rule, exemption, or doctrine; do not present a legal conclusion without naming the supporting rule. ## 4. Analytical scaffolds - Start by isolating each distinct transfer, party, and share block that is actually in scope. - For the issues memo, use an ordinal severity scale stated once at the top and apply it uniformly to each issue. - For each issue, identify: the specific document provision or status flag implicated, why the issue matters for this sale, and the concrete closing or post-closing consequence if unresolved. - If the source materials provide a timing trigger, tie the recommendation to that milestone; otherwise use a relative urgency tied to signing, closing, or transfer-agent processing. - In the waiver, recite the exact transfer at issue in the recitals: transferor, transferee, class, amount, and consideration. - Make the operative consent narrowly tailored: consent only to the identified transfer, while preserving all unmentioned rights, restrictions, and approvals. - State whether the seller represents that the shares being transferred are fully vested or identify any shares that remain subject to repurchase rights and how those rights are handled. - Include conditions to effectiveness for the transferee’s joinder, legal-opinion or other securities-law support if required by the source package, and any transfer-agent deliverables needed for legend removal. - Confirm that, after effectiveness, the transferee takes the shares subject to the remaining transfer restrictions and related obligations. - If a risk cannot be cured by the waiver alone, say so in the memo and flag the separate action needed. ## 5. Vertical / structural / temporal relationships - Distinguish among pre-closing consent, closing-condition deliverables, and post-closing administrative steps. - Separate issuer/board action from holder consent rights; if multiple approving parties are required, identify each role in the order the consents are needed. - Track whether any condition must be satisfied before the transfer-agent will process the transfer versus after the transfer closes. - If the transaction involves more than one class or block, analyze each block separately rather than assuming the same waiver logic applies to all of them. ## 6. Output structure conventions - Produce the issues memorandum as a concise advisory memo with a short risk-scale legend, issue-by-issue analysis, and a concluding Recommended Actions section. - For each issue entry, include the severity label, the affected provision or fact, the legal or contractual basis, and the practical consequence. - The waiver letter should read as a formal consent and waiver, with clear recitals, narrowly framed operative consent, preserved rights language, conditions to effectiveness, and execution blocks for the required signatories. - Use conventional transactional drafting rather than explanatory prose inside the waiver; the memo is where explanation belongs. - Keep the waiver self-contained enough that it can be circulated for signature and implementation without needing the memo to understand the operative consent. - End the memo with imperative action items naming the responsible role and the timing anchor. - Do not broaden the consent beyond the specific transaction described in the source documents.