Gc Review
/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Install
Quick install
npx skills add https://github.com/alirezarezvani/claude-skills/tree/main/c-level-advisor/c-level-agents/skills/gc-reviewnpx skills add alirezarezvani/claude-skills --skill gc-review --agent claude-codenpx skills add alirezarezvani/claude-skills --skill gc-review --agent cursornpx skills add alirezarezvani/claude-skills --skill gc-review --agent codexnpx skills add alirezarezvani/claude-skills --skill gc-review --agent opencodenpx skills add alirezarezvani/claude-skills --skill gc-review --agent github-copilotnpx skills add alirezarezvani/claude-skills --skill gc-review --agent windsurfMore install options
Shorthand — useful for multi-skill repos:
npx skills add alirezarezvani/claude-skills --skill gc-reviewManual — clone the repo and drop the folder into your agent's skills directory:
git clone https://github.com/alirezarezvani/claude-skills.gitcp -r claude-skills/c-level-advisor/c-level-agents/skills/gc-review ~/.claude/skills//cs:gc-review — General Counsel Forcing Questions
Command: /cs:gc-review <plan>
The General Counsel lens. Six questions before any contract, term sheet, IP move, or regulatory commitment. This is a lane gstack has zero of — and one where a single missed clause costs more than a year of engineering.
⚠️ Not legal advice. This command surfaces the right questions to ask before talking to outside counsel. Always engage qualified counsel for binding decisions.
When to Run
- Before signing any contract > $100K or > 1 year
- Before issuing equity (employee grants, advisor grants)
- Before a term sheet response
- Before entering a regulated market (healthcare, fintech, defense)
- Before any open-source license decision in core IP
- Before an M&A LOI
The Six GC Questions
1. IP Ownership
Who owns the IP being created or shared in this transaction?- Work-for-hire vs license vs joint.
- For employees and contractors: written IP assignment in place?
- For OSS: license compatibility checked?
2. Liability & Indemnity
What's the liability cap, and what's carved out from it?- Standard cap: 12 months of fees.
- Carve-outs: IP infringement, data breach, willful misconduct.
- Mutual indemnity desirable.
3. Data Processing
What personal data is involved, and is a DPA in place?- GDPR / CCPA scope?
- Subprocessor flow-down?
- Data residency requirements?
4. Termination & Renewal
What's the termination right, what's the notice period, and what's auto-renew?- Termination for convenience vs cause.
- Notice period (30 / 60 / 90 days).
- Auto-renewal trap?
5. Regulatory Surface
Does this expose the company to a new regulatory regime?- Healthcare → HIPAA.
- Fintech → BSA/AML, state money-transmitter.
- Medical device → FDA, MDR, ISO 13485.
- Data → GDPR, CCPA, state breach laws.
6. Employment / Equity
If this is a hire or contractor: jurisdiction, classification, equity grant, IP assignment?- Misclassification risk?
- Equity vesting standard (4-year, 1-year cliff)?
- Acceleration triggers?
- 409A current?
Workflow
- Read the contract / term sheet end to end
- Run the six questions
- Identify the top-3 issues that need outside counsel review
- Apply the verdict
Output Format
# GC Review: <plan>
**Date:** YYYY-MM-DD
## Document
- Type: <contract / term sheet / grant / DPA>
- Counterparty: <name>
- $ value or scope: <amount>
## Issues
| # | Issue | Risk | Recommendation |
|---|---|---|---|
| 1 | <e.g., uncapped IP indemnity> | HIGH | Cap at fees paid, mutual |
| 2 | <e.g., 5-year auto-renew> | MED | 1-year max, 60-day notice |
| 3 | <e.g., no DPA, EU data> | HIGH | Require DPA before sign |
## Regulatory Trigger
- New regime triggered? <yes/no>
- Specific frameworks: <HIPAA / GDPR / etc.>
## Outside Counsel Action Items
- [ ] <specific item 1>
- [ ] <specific item 2>
- [ ] <specific item 3>
## Verdict
🟢 SIGN AS-IS (rare)
🟡 NEGOTIATE — counter on top-3 issues
🔴 DO NOT SIGN — material risk
Routing
/cs:ciso-review— for any data-touching contract/cs:cfo-review— for any commitment > 1 year or > 1% of revenue/cs:decide— log the verdict after outside counsel review
Workflow Integration with general-counsel-advisor skill
Since v2.5.1, this command is backed by a full skill at ../../../skills/general-counsel-advisor/ with two Python tools:
# Automated contract scan (12 founder-killer patterns)
python ../../../skills/general-counsel-advisor/scripts/contract_risk_scanner.py path/to/contract.txt
# Term sheet scoring (0-100 founder-friendliness)
python ../../../skills/general-counsel-advisor/scripts/term_sheet_analyzer.py path/to/term_sheet.json
The cs-general-counsel-advisor agent orchestrates both tools plus 3 references (contracts playbook, IP + regulatory, term sheet decoder).
Related
- Skill: [
general-counsel-advisor](../../../skills/general-counsel-advisor/SKILL.md) — full skill with Python tools + references - Agent: [
cs-general-counsel-advisor](../../agents/cs-general-counsel-advisor.md) - Compliance execution:
../../../../ra-qm-team/ - Adjacent:
../../../skills/ma-playbook/
---
Version: 1.0.0
SKILL.md source
--- name: gc-review description: /cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface. --- # /cs:gc-review — General Counsel Forcing Questions **Command:** `/cs:gc-review <plan>` The General Counsel lens. Six questions before any contract, term sheet, IP move, or regulatory commitment. This is a lane gstack has zero of — and one where a single missed clause costs more than a year of engineering. > ⚠️ **Not legal advice.** This command surfaces the right questions to ask before talking to outside counsel. Always engage qualified counsel for binding decisions. ## When to Run - Before signing any contract > $100K or > 1 year - Before issuing equity (employee grants, advisor grants) - Before a term sheet response - Before entering a regulated market (healthcare, fintech, defense) - Before any open-source license decision in core IP - Before an M&A LOI ## The Six GC Questions ### 1. IP Ownership **Who owns the IP being created or shared in this transaction?** - Work-for-hire vs license vs joint. - For employees and contractors: written IP assignment in place? - For OSS: license compatibility checked? ### 2. Liability & Indemnity **What's the liability cap, and what's carved out from it?** - Standard cap: 12 months of fees. - Carve-outs: IP infringement, data breach, willful misconduct. - Mutual indemnity desirable. ### 3. Data Processing **What personal data is involved, and is a DPA in place?** - GDPR / CCPA scope? - Subprocessor flow-down? - Data residency requirements? ### 4. Termination & Renewal **What's the termination right, what's the notice period, and what's auto-renew?** - Termination for convenience vs cause. - Notice period (30 / 60 / 90 days). - Auto-renewal trap? ### 5. Regulatory Surface **Does this expose the company to a new regulatory regime?** - Healthcare → HIPAA. - Fintech → BSA/AML, state money-transmitter. - Medical device → FDA, MDR, ISO 13485. - Data → GDPR, CCPA, state breach laws. ### 6. Employment / Equity **If this is a hire or contractor: jurisdiction, classification, equity grant, IP assignment?** - Misclassification risk? - Equity vesting standard (4-year, 1-year cliff)? - Acceleration triggers? - 409A current? ## Workflow 1. Read the contract / term sheet end to end 2. Run the six questions 3. Identify the top-3 issues that need outside counsel review 4. Apply the verdict ## Output Format ```markdown # GC Review: <plan> **Date:** YYYY-MM-DD ## Document - Type: <contract / term sheet / grant / DPA> - Counterparty: <name> - $ value or scope: <amount> ## Issues | # | Issue | Risk | Recommendation | |---|---|---|---| | 1 | <e.g., uncapped IP indemnity> | HIGH | Cap at fees paid, mutual | | 2 | <e.g., 5-year auto-renew> | MED | 1-year max, 60-day notice | | 3 | <e.g., no DPA, EU data> | HIGH | Require DPA before sign | ## Regulatory Trigger - New regime triggered? <yes/no> - Specific frameworks: <HIPAA / GDPR / etc.> ## Outside Counsel Action Items - [ ] <specific item 1> - [ ] <specific item 2> - [ ] <specific item 3> ## Verdict 🟢 SIGN AS-IS (rare) 🟡 NEGOTIATE — counter on top-3 issues 🔴 DO NOT SIGN — material risk ``` ## Routing - `/cs:ciso-review` — for any data-touching contract - `/cs:cfo-review` — for any commitment > 1 year or > 1% of revenue - `/cs:decide` — log the verdict after outside counsel review ## Workflow Integration with `general-counsel-advisor` skill Since v2.5.1, this command is backed by a full skill at `../../../skills/general-counsel-advisor/` with two Python tools: ```bash # Automated contract scan (12 founder-killer patterns) python ../../../skills/general-counsel-advisor/scripts/contract_risk_scanner.py path/to/contract.txt # Term sheet scoring (0-100 founder-friendliness) python ../../../skills/general-counsel-advisor/scripts/term_sheet_analyzer.py path/to/term_sheet.json ``` The `cs-general-counsel-advisor` agent orchestrates both tools plus 3 references (contracts playbook, IP + regulatory, term sheet decoder). ## Related - Skill: [`general-counsel-advisor`](../../../skills/general-counsel-advisor/SKILL.md) — full skill with Python tools + references - Agent: [`cs-general-counsel-advisor`](../../agents/cs-general-counsel-advisor.md) - Compliance execution: `../../../../ra-qm-team/` - Adjacent: `../../../skills/ma-playbook/` --- **Version:** 1.0.0
Related skills 6
to-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Boardroom
/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo.
Brief
/cs:brief <topic> — Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline.
C Level Agents
Founder-mode executive team. 8 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, Chief of Staff) and 17 /cs:* slash commands for forcing-question office hours, multi-role boardroom delibera...
Caio Review
/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.