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 when important context is missing, inconsistent, or needs normalization. Ask only for information that can change the decision.
3. Read 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 for stale, conflicting, confidential, high-stakes, or externally actionable work.
5. Read 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