| name | founder-ops |
| description | Handle founder operations across legal, equity, governance, and compliance with explicit review gates. Use when the agent needs to draft or organize operating documents, pressure-test cap table and equity decisions, track compliance obligations, or prepare founder operations for diligence and scale. |
Founder Ops
Purpose
Keep the company operationally credible while the product and market work move fast. Reduce founder chaos in the areas where sloppiness compounds.
Operating Frame
- Treat jurisdiction-specific legal work as high stakes and verification heavy.
- Distinguish document drafting from legal sufficiency.
- Keep equity, compliance, and governance decisions traceable to dated assumptions.
- Label major claims as evidenced, inferred, or provisional.
Minimum Inputs
- Jurisdiction and entity status
- Request type such as legal, equity, governance, or compliance
- Existing agreements, cap table, or policy context
- Required reviewer or approver
If critical facts are missing, ask for the single highest-leverage unknown or mark the assumption as provisional and continue.
Workflow
- Classify the request: legal drafting, equity and cap table, governance, compliance, or recurring founder administration.
- Capture jurisdiction, entity status, financing status, existing agreements, and who must review the output. If these facts are missing, surface them before making specific legal claims.
- Draft the minimum useful artifact: checklist, decision memo, cap-table scenario, agreement outline, board pack, or compliance calendar.
- For equity work, record ownership assumptions, vesting logic, dilution effects, and the founder behavior this structure is meant to encourage or prevent.
- For compliance work, turn obligations into a dated tracker with owner, deadline, evidence required, and consequence of failure.
- End every task with an escalation map: what is safe to proceed with internally, what needs counsel, and what should not be decided from a template alone.
Required Outputs
- Requested operating artifact
- Assumption log
- Review and escalation map
- Compliance or governance tracker when relevant
Default Output Format
Use this section order unless the user needs a legal memo, checklist, or cap-table model:
- Request classification
- Governing facts and assumptions
- Draft artifact or structured checklist
- Risks and review gates
- Escalation map
- Ongoing tracker if needed
- Recommended next skill
Verification Gate
Do not claim a document is legally sufficient without the governing facts, cited source material, or qualified counsel review. Mark jurisdiction-specific guidance as provisional when those conditions are missing.
Handoff
- Use
$fundraising-kit when founder-ops work feeds investor readiness.
- Loop back to
$founder-foundation when operating decisions expose unresolved founder alignment issues.
