written-consent

Generate compliant remote voting documents for Russian corporate entities.

17|4|Updated May 25, 2026
One-click install
npx skills add https://github.com/AlsKozlov/ru-legal --skill written-consent-alskozlov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: written-consent
Source: https://github.com/AlsKozlov/ru-legal/tree/main/packs/corporate-law/skills/written-consent
Command: npx skills add https://github.com/AlsKozlov/ru-legal --skill written-consent-alskozlov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of invalid corporate decisions caused by procedural errors when conducting remote (заочное) voting for Russian limited liability companies (ООО) and joint-stock companies (АО/ПАО), which requires strict adherence to specific legal formalities under Russian corporate law.

Core Features & Use Cases

  • Eligibility Validation: Checks if a proposed voting question is permitted for remote voting under ФЗ-208 (for АО) and ФЗ-14 (for ООО), including prohibitions on electing boards of directors or approving annual reports for joint-stock companies.
  • Full Document Generation: Creates all required procedural documents including voting ballots, participant notifications, and formal meeting minutes tailored to the entity type.
  • Compliance Guardrails: Automatically flags mandatory requirements like notarization for ООО decisions, minimum notification timelines (21-30 days), and quorum rules to avoid void outcomes.
  • Use Case: A corporate secretary for a Russian LLC needs to hold a remote vote to approve a related-party transaction; this skill generates all compliant documentation and alerts the user to mandatory notarization requirements to ensure the decision is legally valid.

Quick Start

Use the written-consent skill to draft a complete set of compliant remote voting documents for my ООО's upcoming vote to approve a 10% stake sale in a subsidiary, including the ballot, notification to all participants, and formal meeting minutes.

Frequently Asked Questions about written-consent

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

FAQPage Schema
How do I draft compliant remote voting documents for a Russian LLC?

To draft compliant remote voting documents for a Russian LLC, you need automated generation of ballots, notifications, and minutes adhering to ФЗ-14 procedural requirements. This ensures mandatory notarization and quorum rules are flagged to prevent void corporate decisions.

What questions are prohibited for remote voting in Russian joint-stock companies?

Under ФЗ-208, Russian joint-stock companies are prohibited from holding remote voting on certain questions, including electing boards of directors or approving annual reports. Eligibility validation checks proposed voting questions against these legal prohibitions before document generation.

What are the notification timeline requirements for заочное голосование in Russia?

Notification timeline requirements for заочное голосование in Russia mandate sending participant notifications 21 to 30 days before the vote. Compliance guardrails automatically flag these minimum notification timelines to ensure corporate decisions remain legally valid under ГК РФ.

Can I use automated legal documentation for related-party transaction approvals in an ООО?

Yes, you can use automated legal documentation for related-party transaction approvals in an ООО. The workflow generates the required voting ballots, participant notifications, and formal meeting minutes while alerting you to mandatory notarization requirements under Russian corporate law.

Why do corporate decisions get voided during remote shareholder voting in Russia?

Corporate decisions get voided during remote shareholder voting in Russia due to procedural errors like missing notarization for ООО decisions, insufficient notification timelines, or failing quorum rules. Automated compliance guardrails flag these mandatory requirements to prevent invalid outcomes.