coml-cold-start-interview

Imported from Matrixx0070/sudo-skills (docs/skills/coml-cold-start-interview/SKILL.md). Install upstream with npx skills add Matrixx0070/sudo-skills --skill coml-cold-start-interview. Copyright stays with the author.

When to use

Use this the first time the commercial-legal skills are set up for an organization, when no playbook exists yet. It gathers the raw material — standard positions, risk tolerance, and who decides what — so every later review measures against the company's own bar, not a generic one.

Not for: adjusting an existing playbook (use coml-customize), reviewing a specific contract (coml-review), or organizing an active matter (coml-matter-workspace).

Method

1. Capture the basics: legal entity name, jurisdiction of incorporation, and preferred governing law and venue.
2. Elicit standard positions for the three contract families using the reference tables as a checklist — NDA term and residuals, SaaS liability cap and data ownership, vendor IP and insurance. Record the preferred and the fallback for each.
3. Probe risk tolerance: how much liability exposure is acceptable, appetite for one-sided terms, and any absolute red lines.
4. Define signing authority tiers: who can sign at what dollar value and which terms always require sign-off.
5. Escalation gate — establish it now: confirm who counsel is (internal or outside firm) and the triggers that route to them. If there is no counsel relationship, that gap is itself the first thing to escalate before any deal is signed.
6. Capture the renewal-notice process: who owns the calendar and how reminders are set.
7. Output a playbook stub that coml-customize can refine.

Example

Interview of a 40-person SaaS company: entity Delaware C-corp, prefers Delaware law. NDA: mutual, 3-year, no residuals. SaaS-as-customer: 12-month cap, customer owns data, 60-day notice acceptable as fallback. Signing authority: founder any value; ops lead up to $25K non-gate terms. Counsel: outside firm, engaged for liability/IP/data terms. Renewal owner: ops lead. Gap found: no formal renewal calendar — flagged to stand up coml-renewal-tracker.

Pitfalls

• Collecting preferred positions but not fallbacks, so reviewers have nothing to negotiate toward.
• Skipping signing authority, leaving it unclear who can actually agree to what.
• No named counsel or triggers, so escalation has nowhere to go.
• Treating the interview as one-time — capture enough that coml-customize can iterate.

Output format

PLAYBOOK STUB — <company> | <date>
Entity: <name> · jurisdiction · preferred law/venue
Standard positions:
  - NDA: <term / mutuality / residuals — preferred | fallback>
  - SaaS/MSA: <cap / data / renewal — preferred | fallback>
  - Vendor: <IP / insurance / termination — preferred | fallback>
Risk tolerance: <appetite + red lines>
Signing authority: <tier → who / limit>
Counsel + escalation triggers: <who / when>
Renewal process: <owner / reminder cadence>
Gaps to close: <items>

Reference

Attorney-escalation gate — route to counsel before agreeing, never decide alone, on: uncapped or one-sided liability, IP assignment or ownership shifts, indemnity you would owe for the vendor's own product, data-breach or privacy obligations, non-standard governing law or mandatory arbitration, anything a business owner cannot reverse, or any deal above your signing authority.

NDA clauses

SaaS / MSA clauses

Vendor / services clauses

Renewal-notice tracking