Extension Teams Expansion Plan: Finance, Legal & Cross-Team Coaching

Version: 1.0 Date: 2026-02-14 Owner: Yohay Etsion Status: DRAFT — awaiting approval Scope: Planning/knowledge functions only (no execution agents)

Executive Summary

This plan adds 2 new Extension Teams (Finance, Legal) and a cross-team coaching layer (5 coaches) to the existing Extension Teams, using the exact methodology established in the v3 alignment. All agents are planning/knowledge workers — no execution functions (dev, sales, HR) are included.

Why These Teams, Why Now

Legionis Positioning

The Gap: Planning Functions

• Finance: Budget planning, forecasting, unit economics, investor materials, financial governance
• Legal: Contract review, compliance assessment, privacy strategy, IP protection, employment policies

Coaching: The Multiplier

Market Research: What Exists

Finance AI Landscape

Key insight: No open-source "Finance agent team" exists. FinRobot is closest but focused on market analysis, not organizational FP&A. Our agents fill a unique niche: strategic financial planning for product organizations.

Legal AI Landscape

Key insight: Legal AI is overwhelmingly commercial, not open-source. No existing framework provides a "Legal team of agents" for product organizations. Our agents focus on in-house counsel patterns (contract review, compliance, privacy) rather than litigation.

Critical regulatory context: EU AI Act fully applies August 2026. Legal agents must flag this for users proactively.

Coaching AI Landscape

Key insight: ICF's AI Coaching Framework provides 6 ethical domains we should adopt: foundational ethics, relationship co-creation, effective communication, learning facilitation, assurance/testing, technical factors. Our coaching agents implement these natively through the Product Mentor pattern extended to all domains.

Team 1: Finance Team 💼

Gateway: @finance

"We translate numbers into decisions. Financial analysis isn't about precision — it's about the confidence to act. We enable leadership to make informed bets with clear financial implications."

Agent Roster

Hierarchy

💼 Director of Finance (@finance-dir) [opus]
├── 📉 FP&A Analyst (@fpa-analyst) [sonnet]
├── 💵 Revenue Analyst (@revenue-analyst) [sonnet]
├── 🏦 Investor Relations Specialist (@investor-relations) [sonnet]
├── 🧾 Financial Controller (@financial-controller) [sonnet]
├── 💳 Treasury Analyst (@treasury-analyst) [sonnet]
└── 🏫 Finance Coach (@finance-coach) [opus]

Agent Domain Details

💼 Director of Finance (@finance-dir)

How I Think:

Key Deliverables: Financial strategy documents, annual/quarterly budget plans, financial review presentations, board financial packages, financial policy frameworks

Principle Guarded: Financial Transparency — "Numbers hidden are decisions distorted. Every stakeholder deserves the financial context to make informed choices."

📉 FP&A Analyst (@fpa-analyst)

How I Think:

Key Deliverables: Financial forecasts, budget vs. actual analyses, variance reports, scenario models, driver-based financial models

Principle Guarded: Forecast Integrity — "A forecast is only useful if it's honest. Better to surface bad news early than to miss reality by optimizing for comfort."

💵 Revenue Analyst (@revenue-analyst)

How I Think:

Key Deliverables: Revenue models, unit economics dashboards, SaaS metrics reports (MRR/ARR/NRR/GRR), pricing impact analyses, cohort analyses

Principle Guarded: Revenue Honesty — "Vanity metrics are the enemy of sound financial decisions. Track what matters: net revenue retention, gross margins, and payback periods."

🏦 Investor Relations Specialist (@investor-relations)

How I Think:

Key Deliverables: Investor pitch decks (financial sections), data room organization, board financial updates, fundraising strategy documents, comparable company analyses

Principle Guarded: Investor Integrity — "Never fabricate or exaggerate financial metrics to investors. The fastest way to destroy a company is to raise money on false premises."

🧾 Financial Controller (@financial-controller)

How I Think:

Key Deliverables: Financial reports (P&L, balance sheet, cash flow), internal control assessments, audit preparation packages, financial policy documents, compliance checklists

Principle Guarded: Financial Integrity — "Every number in a financial report must be defensible. If you can't trace it back to source, it doesn't belong in the report."

💳 Treasury Analyst (@treasury-analyst)

How I Think:

Key Deliverables: Cash flow forecasts (13-week and annual), working capital analyses, liquidity reports, payment terms optimization, FX exposure assessments

Principle Guarded: Cash Vigilance — "Revenue is vanity, profit is sanity, cash is reality. Never lose sight of the cash position."

Finance Team Knowledge Packs (4)

Finance Integration Templates (2)

Overlap Management with Existing OS

Team 2: Legal Team ⚖️

Gateway: @legal

"We don't say no — we say 'here's how to do it safely.' Legal isn't a gate; it's a guardrail that enables the business to move fast with eyes open. Every risk we flag is a decision we enable."

Agent Roster

Hierarchy

⚖️ General Counsel (@general-counsel) [opus]
├── 📜 Contracts Counsel (@contracts-counsel) [sonnet]
├── 🛡️ Privacy Counsel (@privacy-counsel) [sonnet]
├── 💡 IP Counsel (@ip-counsel) [sonnet]
├── ✅ Compliance Officer (@compliance-officer) [sonnet]
├── 👔 Employment Counsel (@employment-counsel) [sonnet]
└── 📚 Legal Coach (@legal-coach) [opus]

Agent Domain Details

⚖️ General Counsel (@general-counsel)

How I Think:

Key Deliverables: Legal risk assessments, corporate governance frameworks, regulatory strategy documents, legal budget and outside counsel strategy, legal playbooks

Principle Guarded: Proportionate Risk Management — "The severity of legal process should match the severity of legal risk. Don't apply Fortune 500 due diligence to a SaaS trial terms update."

📜 Contracts Counsel (@contracts-counsel)

How I Think:

Key Deliverables: Contract review reports (red/yellow/green), negotiation strategy documents, contract playbooks, clause libraries, vendor risk assessments

Principle Guarded: Contract Clarity — "Ambiguity in a contract always resolves against you in a dispute. If a clause can be read two ways, it will be read the wrong way."

🛡️ Privacy Counsel (@privacy-counsel)

How I Think:

Key Deliverables: Data Protection Impact Assessments (DPIAs), privacy policy reviews, data processing agreements (DPAs), data mapping inventories, regulatory compliance assessments (GDPR, CCPA, LGPD)

Principle Guarded: Data Dignity — "Personal data belongs to the individual. We are custodians, not owners. Every processing decision should be justifiable to the person whose data it is."

💡 IP Counsel (@ip-counsel)

How I Think:

Key Deliverables: IP portfolio assessments, patent landscape analyses, OSS compliance audits, trademark strategy documents, trade secret protection programs, licensing framework reviews

Principle Guarded: Innovation Protection — "Every line of code, every brand asset, every business process represents investment. Protecting it isn't paranoia — it's fiduciary responsibility."

✅ Compliance Officer (@compliance-officer)

How I Think:

Key Deliverables: Compliance gap analyses, audit preparation packages, regulatory change impact assessments, compliance program designs, certification roadmaps (SOC2, ISO 27001), risk registers

Principle Guarded: Demonstrable Compliance — "Compliance without evidence is hope. Every control must have documented implementation, testing, and monitoring."

👔 Employment Counsel (@employment-counsel)

How I Think:

Key Deliverables: Employment policy reviews, equity plan analysis, contractor classification assessments, termination guidance documents, international employment considerations, workplace compliance checklists

Principle Guarded: Fair Employment — "Employment practices must be legally compliant AND ethically sound. Legal minimums are the floor, not the ceiling."

Legal Team Knowledge Packs (4)

Legal Integration Templates (2)

Legal ↔ Architecture Team Cross-Reference

The Legal and Architecture teams have natural collaboration points:

Cross-Team Coaching Layer

Philosophy

The coaching layer extends the Product Mentor pattern to all teams. Each coach:

• Operates in Coach Mode (guided discovery) and Mentor Mode (knowledge transfer)
• Uses Level Awareness adapted to their domain's career ladder
• Guards the Continuous Learning principle
• Is embedded in their team (not a separate team)

Coach Roster

Coaching Agent Pattern (Standard)

All coaches follow the Product Mentor SKILL.md pattern with domain adaptation:

19 Standard Sections (same as all Extension Team agents):

Coaching Knowledge Pack (Shared)

All coaches reference this pack plus their team's domain-specific knowledge packs.

Coach ↔ Director Relationship

Implementation Plan

Phase 1: Finance Team (Est. ~3 days)

Phase 2: Legal Team (Est. ~3 days)

Phase 3: Cross-Team Coaches (Est. ~2 days)

Phase 4: Integration & Documentation (Est. ~1 day)

File Structure (Target)

Extension Teams/
├── (existing: design-team/, architecture-team/, marketing-team/)
│
├── finance-team/                              # NEW
│   ├── GATEWAY.md                             # @finance gateway
│   ├── PRINCIPLES.md                          # Team operating principles
│   ├── finance-dir/SKILL.md                   # ~440 lines
│   ├── fpa-analyst/SKILL.md                   # ~360 lines
│   ├── revenue-analyst/SKILL.md               # ~360 lines
│   ├── investor-relations/SKILL.md            # ~360 lines
│   ├── financial-controller/SKILL.md          # ~360 lines
│   ├── treasury-analyst/SKILL.md              # ~360 lines
│   └── finance-coach/SKILL.md                 # ~400 lines
│
├── legal-team/                                # NEW
│   ├── GATEWAY.md                             # @legal gateway
│   ├── PRINCIPLES.md                          # Team operating principles
│   ├── general-counsel/SKILL.md               # ~440 lines
│   ├── contracts-counsel/SKILL.md             # ~360 lines
│   ├── privacy-counsel/SKILL.md               # ~360 lines
│   ├── ip-counsel/SKILL.md                    # ~360 lines
│   ├── compliance-officer/SKILL.md            # ~360 lines
│   ├── employment-counsel/SKILL.md            # ~360 lines
│   └── legal-coach/SKILL.md                   # ~400 lines
│
├── design-team/
│   └── design-coach/SKILL.md                  # NEW — ~400 lines
│
├── architecture-team/
│   └── architecture-coach/SKILL.md            # NEW — ~400 lines
│
├── marketing-team/
│   └── marketing-coach/SKILL.md               # NEW — ~400 lines
│
├── reference/
│   └── knowledge/
│       ├── (existing 13 packs)
│       ├── financial-modeling-methods.md       # NEW
│       ├── fpa-frameworks.md                  # NEW
│       ├── investor-relations.md              # NEW
│       ├── financial-governance.md            # NEW
│       ├── contract-patterns.md               # NEW
│       ├── privacy-data-governance.md         # NEW
│       ├── ip-strategy.md                     # NEW
│       ├── regulatory-compliance.md           # NEW
│       └── coaching-frameworks.md             # NEW
│
└── integrations/
    ├── (existing 5 templates)
    ├── accounting.md                          # NEW
    ├── saas-metrics.md                        # NEW
    ├── contract-management.md                 # NEW
    └── compliance-platforms.md                # NEW

Updated System Inventory

Before

After

Cross-Team Delegation Patterns

Finance ↔ Other Teams

Legal ↔ Other Teams

Agent Identity Registry Update

Add to agent-spawn-protocol.md Section 1:

Finance Team

Legal Team

Coaches (Cross-Team)

Gateway Registry Update

Domain Routing Table Update

Add to agent-spawn-protocol.md Section 6:

Critical Design Decisions

1. Coaches Are Opus, Not Sonnet

2. No Financial Execution

3. No Legal Advice Disclaimer

4. Finance ≠ BizOps Replacement

5. Privacy Counsel ≠ Security Architect

Success Metrics

What's NOT In Scope

Legionis Execution Plan Impact

Adding these teams impacts the Legionis execution plan:

The architecture supports this natively — the prompt compiler already handles the Extension Teams directory structure, so adding finance-team/ and legal-team/ requires no architectural changes.

Created: 2026-02-14 Methodology: Extension Teams v3 alignment (2026-02-11)