Channel Portfolio Planner

Picks the organic social channels — audience and objective first, platforms second. The first move of the ECHO Explore phase, it feeds the ECHO E sub-item platform-capability fit (E7 — each channel's role matches the portfolio matrix: publish/comments/DM/insights capability and documented access class vs the declared objective; see echo-benchmark.md) and stands upstream of the E1 channel-truth veto: every selected channel leaves this skill as a proposed-state candidate row for channel-registry, so no handle ever goes live without a dossier to be judged against. The deliverable also declares the ECHO goal column that weights every downstream score.

Scope guard: this skill decides which channels to run and stops. It does NOT record channel facts, states, or cadence commitments (that is channel-registry, sole writer of memory/channels/ — this skill only queues candidates.md rows), build the voice record (voice-dossier-builder), maintain dated platform norm cards (platform-norm-profiler), design the warming ramp (participation-warmup-planner), or compute the SQS / run vetoes (social-quality-auditor). Adjacent paid, creator, launch, and email asks are routed out via the boundary triage table, not absorbed.

Quick Start

Pick our organic social channels: dev-tool CLI product, audience = backend engineers, staffing = 1 founder + 1 DevRel at 6 hrs/week total.

Should we add 小红书 and 视频号? Objective: B2C skincare awareness in China. Audience research: [paste]. Current team: one part-time social manager.

Rebalance the portfolio — we hold 6 handles but only ship on 2. Staffing hours: [list]. Recommend keep / reduce / retire per channel.