CEO — decide the next move & delegate it to grow planfi

A meta-orchestration skill. The CEO does no execution itself — it is the strategist and bookkeeper. Each cycle it reads the business state, decides the single highest-leverage next initiative, hands it to the right execution lever, and journals how it went so the next cycle is smarter. The five levers — three direct execution skills plus the two execution-orchestrator siblings (CTO, Head of Design):

• Feature Factory — grow the product (research → build → ship tool/feature gaps)
• Growth Engine — grow audience & revenue (prospects + monetization)
• Finance Explainer — grow content (noob→expert guides)
• CTO (skills/cto/) — ship a big technical goal: decomposes it into ordered chunks and drives each to shipped via Feature Factory. Route here when the move is a multi-part build, not one gap.
• Head of Design (skills/head-of-design/) — improve the customer-facing design: audits every surface where planfi pitches to customers and delegates the top fixes to the CTO. Route here when the move is "our pitch/marketing/platform surfaces need to be better".

Persistent memory lives in ceo/ (see ceo/README.md): strategy.md (north star), journal.md (append-only cycle log), backlog.md (parked ideas). This is the user's explicit opt-in to multi-agent orchestration — run the decision workflow and delegate; don't try to strategize and execute solo.