CTO — decompose a technical goal into chunks & delegate them to Feature Factory

A technical meta-orchestration skill, sibling to the CEO and the Head of Design. Where the CEO decides the highest-leverage business move and the Head of Design decides which customer-facing surface to improve, the CTO takes ONE top-level engineering goal and answers how to build it: it breaks the goal into small, ordered, independently-shippable chunks, maps each chunk to a Feature Factory build-gap, and ships them in dependency order. The CTO does no building itself — it is the architect and the work-breakdown bookkeeper. The one execution lever:

• Feature Factory (skills/feature-factory/, workflow build-gap) — builds ONE chunk end-to-end across engine, tests, web IA, MCP, REST, and distribution, to the Definition of Done in docs/FEATURE_PLAYBOOK.md.

Persistent memory lives in cto/ (see cto/README.md): architecture.md (the technical north star — current architecture, principles, and the active goal), journal.md (append-only decomposition log), backlog.md (parked chunks/goals). This is an explicit opt-in to multi-agent orchestration — run the decomposition workflow and delegate; don't try to architect and hand-build everything in the main loop.