Install
$ agentstack add skill-rohasnagpal-legal-ai-skills-restructuring-documenter ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Restructuring Documenter
Purpose
Turn a restructuring objective into a sequenced, auditable implementation plan in which ownership, assets, liabilities, approvals, consents, filings, consideration, conditions, and post-closing records move together.
Required inputs
Obtain:
- the commercial objective, proposed end state, deadline, and acceptable alternatives;
- every entity, jurisdiction, ownership interest, constitutional document, and current group chart;
- cap tables, debt, security, guarantees, material contracts, licences, assets, liabilities, employees, IP, real estate, litigation, tax attributes, and financial statements;
- lender, investor, minority, employee, regulator, counterparty, court or tribunal constraints;
- proposed consideration, funding, valuations, accounting and tax assumptions; and
- prior steps, signed documents, filings, approvals, and whether any action has already taken effect.
Treat the current and target structures, entities, jurisdictions, assets and liabilities in scope, and commercial objective as blocking. Do not choose a restructuring route by assuming tax neutrality or regulatory availability.
Method
- Draw
beforeandafterstructure maps. Reconcile legal ownership, beneficial ownership, voting, debt, security, guarantees, licences, employees, and operational dependencies. - Develop viable route options and state assumptions. Compare direct transfer, merger, demerger, contribution, distribution, capital reduction, buyback, conversion, novation, liquidation, or other mechanism only where available under verified law.
- For each route, identify legal, tax, accounting, regulatory, creditor, employee, minority, contractual, timing, cost, and execution dependencies. Route specialist conclusions to qualified sources.
- Build an approval matrix across boards, committees, shareholders or classes, lenders, investors, counterparties, regulators, courts, exchanges, tax authorities, employees, trustees, and other stakeholders.
- Sequence conditions and steps. Identify what must happen before signing, at signing, before closing, simultaneously at closing, after closing, and by each long-stop date. Prevent circular or unsecured dependencies.
- Create the document list: structure paper, valuations, solvency or fairness materials, resolutions, notices, consents, transaction agreements, transfer instruments, novations, releases, employment documents, IP and property instruments, filings, certificates, funds flow, and closing confirmations.
- Track each asset and liability. Specify transfer mechanism, consent, registration, tax or duty, effective date, consideration, custody, and evidence. Do not assume business transfer language moves assets requiring separate formality.
- Address creditor and stakeholder protection: security release or regrant, guarantees, covenants, minority rights, employee consultation or transfer, pensions, licences, permits, data, litigation, and customer or supplier continuity.
- Build the closing process with responsible owner, original or electronic document, signature method, escrow or release rule, filing order, evidence, and fallback if a condition fails.
- Create post-closing remediation and records: registers, certificates, beneficial ownership, accounting entries, tax elections or returns, notifications, licence updates, data migrations, document retention, dormant entity actions, and final structure verification.
Output
Produce:
- Options and assumptions paper.
- Approval and consent matrix.
- Step plan — sequence, owner, dependency, document, deadline, and completion evidence.
- Document and filing list.
- Closing checklist and funds-flow dependencies.
- Post-closing and residual-risk schedule.
Guardrails
- Do not state that a route is tax neutral, stamp efficient, solvent, creditor proof, or regulator approved without specialist verification.
- Do not assume assets, licences, employees, contracts, security, liabilities, or litigation transfer automatically.
- Do not backdate steps or use documents to imply a sequence that did not occur.
- Do not ignore minority, creditor, employee, insolvency, foreign investment, competition, securities, or beneficial-ownership consequences.
- Do not treat a group-company relationship as authority to transfer value without approvals, consideration, duties, and related-party analysis.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: rohasnagpal
- Source: rohasnagpal/legal-ai-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.