Topy ai ceo core

TOPY AI CEO Core

Use this as the default executive reasoning skill when the task is not a product-specific TOPY dashboard workflow.

When to use

Use this skill for:

• strategic bets and market entry
• prioritization and resource allocation
• organizational design and operating model choices
• OKR / KPI design and review
• fundraising and capital planning
• M&A, partnership, or build-vs-buy decisions
• crisis response and exec transitions
• stakeholder alignment across board, investors, employees, and partners
• competitive response and war-gaming
• bias checks, uncertainty handling, and quantitative trade-offs

If a narrower TOPY skill fits better, use that skill first. Use this one when the problem is cross-functional, ambiguous, or board-level.

Working sequence

1. Classify the decision.
2. State the real question.
3. Surface constraints, stakeholders, deadlines, and non-negotiables.
4. Pick the smallest useful playbook.
5. Generate at least 3 options plus do nothing when relevant.
6. Check bias and uncertainty.
7. End with a recommendation and next steps.

Decision types

• Type 1: irreversible or costly-to-reverse decisions
• Type 2: reversible experiments
• Crisis: time-critical response
• Strategic bet: long-horizon, high-uncertainty move
• Operating design: org, process, OKR, KPI, or capacity decisions
• Capital decision: fundraising, runway, budget, or investment planning
• Stakeholder decision: board, investor, employee, or partner alignment
• Competitive move: pricing, launch, position, or market entry response

Playbooks

Load only the reference that fits the moment:

• Strategy and prioritization: references/strategy-and-priority.md
• Operating model, OKRs, KPIs, and fundraising: references/operating-and-capital.md
• Crisis and stakeholder handling: references/crisis-and-stakeholders.md
• Competitive and market moves: references/competitive-and-market.md
• Debiasing and uncertainty: references/debiasing-and-uncertainty.md
• Quantitative tools: references/quantitative-tools.md

Examples and evals

• Real prompt patterns: examples/
• Lightweight evaluation prompts: evals/evals.json

Default output shape

Prefer a brief, structured decision memo:

## Decision Brief: [Title]

**Decision Type:** [Type]
**Urgency:** [Immediate / This Week / Can Wait]
**Confidence Level:** [High / Medium / Low]

### The Question
[The real decision in one sentence]

### Context & Constraints
[Facts, deadlines, resources, and non-negotiables]

### Stakeholders
[Who matters, who can block, who needs to be informed]

### Options
[At least 3 options, plus do nothing when relevant]

### Recommendation
[What to do and why]

### Risks to Monitor
[Key failure modes and mitigations]

### Next Steps
[Immediate actions, owners, and review point]

Rules

• Do not give generic business advice when a decision needs a recommendation.
• Do not hide trade-offs.
• Do not use fake precision; show ranges when uncertainty is real.
• For crisis, lead with immediate containment, then stabilization, then root cause.
• For quantitative questions, use the script helpers instead of inventing math.
• For uncertain decisions, say what evidence would change your mind.
• If the user asks for a repeatable test, point them to the examples or evals before improvising.