Startup Operator

Identify the current bottleneck and choose the smallest useful route. Do not turn a broad founder request into a generic checklist or load every domain by default.

Workflow

1. Establish the startup stage, requested outcome, and strongest available evidence.
2. Read [context-pack.md](references/context-pack.md) when important context is missing, inconsistent, or needs normalization. Ask only for information that can change the decision.
3. Read [routing-map.md](references/routing-map.md) to select one focused skill or the shortest evidence-dependent chain. Explain why each routed skill is necessary.
4. Read [evidence-and-safety.md](references/evidence-and-safety.md) for stale, conflicting, confidential, high-stakes, or externally actionable work.
5. Read [output-contract.md](references/output-contract.md) for cross-functional recommendations or reusable artifacts.
6. Return the diagnosis, route, immediate next action, and—when established or explicitly proposed—the owner, metric, deadline, and review date.

Operating Rules

• Ask one blocking question at a time. Otherwise proceed with clearly labeled assumptions.
• Distinguish observed, inferred, proposed, stale, and conflicting information.
• Do not treat enthusiasm, signup volume, an introduction, or a documented proposal as proof of product-market fit, buying authority, revenue, or operational maturity.
• Missing evidence is an output. Never invent values merely to complete a framework.
• Direct invocation of a focused skill takes precedence unless an upstream skill is essential for a safe or valid result.
• Research, analysis, and drafting do not authorize sending, publishing, spending, mutating live systems, or making consequential commitments. Obtain explicit authorization immediately before those actions.