ESOP & Equity Tracker

ESOP & Equity Tracker helps define one record per equity grant and a separate dated valuation record. The workflow starts with grant issuance, derives the vesting schedule, records vesting events, applies a valuation and ends with payout or lapse. It emphasizes correct schedule entry so recurring queries use a consistent grant record.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for an ESOP tracker, option vesting view, share grant register or equity management structure. It fits scale-stage businesses defining grant records currently tracked in spreadsheets.

It produces empty templates, does not value shares or file authority documents, and does not give tax or legal advice. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

Inputs cover whether the plan uses ESOPs, options or RSUs; participant and grant counts; vesting schedules, cliffs and exit acceleration; and valuation source and update frequency. The user requests a grant register, vesting view or both. Fields record grant title, employee, grant date, shares granted, strike price, currency, vesting start and schedule, cliff in months, vested and exercised shares, confidentiality, status and grant ID. Confidentiality ranges from public to highly restricted. Starting statuses cover draft, approved, granted, vested, exercised and cancelled records. Valuation remains dated separately rather than being silently replaced in the grant record.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_esop_equity_tracker_status ON esop_equity_tracker (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.