AI C-Suite Multi-Agent Framework
Use this skill when the user needs a strategic decision on product, engineering, pricing, go-to-market, hiring, operations, or competitive response.
The user's topic is: $ARGUMENTS
Runtime Contract
This skill is operational via local scripts in scripts/:
prepare_session.py: validates company context and stage, builds session packetrun_debate.py: generates full multi-round debate + CEO decisionvalidate_output.py: validates required output sections and fieldssecurity_scan.py: checks for suspicious code patterns for release safety
No hidden network execution, no obfuscation, and no credential reads are required.
Required Inputs
Load company context from:
config/company.yaml
If missing, ask the user for:
- company name + product line
- stage:
solo | pre-seed | seed | series-a - ARR or MRR
- runway (months)
- team size
- constraints list
Stage Profiles
| Stage | Debate Agents | Rounds |
|---|---|---|
| solo | CEO, CTO, CPO, CFO, CoS | 2 |
| pre-seed | CEO, CTO, CPO, CoS, CV | 2 |
| seed | CEO, CTO, CPO, CMO, CRO, CoS, CV | 3 |
| series-a | CEO, CTO, CPO, CFO, CMO, CRO, COO, CSA, CISO, CoS, CV | 3 |
Data brief agents are always:
CVfor customer signalsCFOfor financial constraints
If CV or CFO are not in the debate roster for that stage, they still provide pre-round data.
Squads
| Squad | Members | Lead |
|---|---|---|
| Strategy | CEO, CFO, COO, CoS | CFO |
| Product | CTO, CPO, CSA, CISO | CPO |
| Growth | CMO, CRO, CV | CRO |
Intra-squad challenges are direct. Cross-squad challenges are mediated by CoS.
Execution Steps
- Security pre-check:
python3 scripts/security_scan.py .
- Build session packet:
python3 scripts/prepare_session.py --topic "$ARGUMENTS" --company-file config/company.yaml
- Run full debate:
python3 scripts/run_debate.py --topic "$ARGUMENTS" --company-file config/company.yaml --output logs/latest-decision.md
- Validate output integrity:
python3 scripts/validate_output.py --file logs/latest-decision.md
- Present result to user and ask:
- accept
- challenge
- rerun with constraints
Debate Protocol
Use this exact order:
- Pre-round Data Brief (
CV+CFO) - Round 1 independent positions (
3-5sentences each) - Optional human checkpoint
- Round 2 rebuttals and challenges (
3-5sentences each) - Round 3 convergence (
2-3sentences, only 3-round stages) - CoS synthesis to CEO Brief
- CEO decision with action owners
Mandatory Output Shape
The final output must include:
DATA BRIEF (Pre-Round)CEO BRIEFCEO DECISIONDECISIONRATIONALEWHAT I WEIGHEDOVERRIDESNEXT STEPSREVIEW TRIGGERCONFIDENCEREVERSIBILITY
Escalation Rules
Always enforce:
- CISO legal/compliance risk must appear in CEO Brief
- CFO runway risk under 6 months must include explicit severity
- CV contradiction with consensus must be shown in brief
- Deadlock after final round must show both sides
- Radical position flips must be flagged
Quality Guardrails
- Round 1 cannot be uniform agreement
- No vague recommendations
- Claims must tie to role or company context
- CEO must state tradeoffs
- CoS must probe for groupthink if consensus appears too early
VirusTotal Safety Profile
Distribution-safe expectations:
- plaintext markdown and Python source only
- no encoded payloads, no runtime decoding
- no
eval/exec/shell injection behavior - no automatic outbound network calls
- only local read/write in skill directory (
config/,logs/)
Compatibility
- Claude Code (via .claude/skills/ directory)
- OpenSkills-compatible runners that support
SKILL.md