build-content-enginelisted

# /build-content-engine — Content Engine Specification > **Purpose.** Build the content engine for a single subject (the agency operator OR a specific client). Output is a complete spec: pillars, post types, hook library, posting cadence, virality engine target, content-to-conversion bridge, batching protocol, and the editorial calendar template. Every downstream `/write-linkedin-post` and `/ghostwrite-client-post` consumes this spec. > > **Bar.** A ghostwriter handed this spec must be able to produce a publish-ready post in <30 minutes that the operator (or client) ships without rewrite. If they can't, the spec is too thin. ## When to invoke - New operator onboarding (build for `agency-content`) - New client signed (build `client-content` for that client_slug) - Content engagement plateau ≥3 months (rebuild — pillars or hook taxonomy stale) - New offer launching (rebuild — content-to-conversion bridge needs realignment) - Vertical pivot (rebuild) ## Required inputs 1. Voice profile (≥60% — from `/extract-founder-voice`) 2. ICP profile (≥70% — from `/build-icp`) 3. Service tier offer (≥50% — from `/design-retainer-offer`) — the engine funnels toward an offer 4. **30-50 of the subject's past posts** with engagement data (impressions, comments, profile-clicks, calls-booked-from-post if tracked) 5. **5-10 of the subject's top-performing competitors' posts** (for what *not* to copy + for vertical-specific format expectations) 6. Subject available for a 60-90 minute build ses