一键导入
distribution-plan
Use when planning social, community, PR, founder-led content, newsletters, audience building, or recurring distribution between launches.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when planning social, community, PR, founder-led content, newsletters, audience building, or recurring distribution between launches.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when writing or rewriting website copy: homepages, landing pages, pricing pages, product pages, feature pages, hero sections, headlines, subheads, CTAs, value propositions, taglines, and above-the-fold messaging. Do not use for email sequences, blog posts, longform X articles, or platform-specific ad copy.
Use when planning a product launch, feature release, waitlist, beta, public announcement, relaunch, Product Hunt-style push, repeated feature launch system, launch-week checklist, or multi-channel GTM rollout.
Use when writing or rewriting longform X/Twitter articles, X Articles, founder essays, launch essays, growth teardowns, product breakdowns, build-in-public stories, or sharp startup takes that need X-native hooks, tone, pacing, and structure. Use for X Articles and long posts, not blog SEO posts, lifecycle emails, or landing page copy.
Use when turning a marketing, growth, CRO, pricing, onboarding, email, ad, or acquisition idea into a useful experiment or test plan.
Use when optimizing a site or brand to show up in AI answers, LLM citations, AI search, product recommendations, and category answers.
Use when auditing, planning, or debugging marketing measurement, conversion tracking, GA4, GTM, UTMs, pixels, CRM attribution, funnel reporting, or dashboard trust.
| name | distribution-plan |
| description | Use when planning social, community, PR, founder-led content, newsletters, audience building, or recurring distribution between launches. |
Create a repeatable plan for turning company activity into posts, newsletters, community updates, PR angles, and partner promotion.
Find what the team can repeatedly talk about:
If there is no source material, plan collection habits before a posting schedule.
Route source material by job:
Then choose surfaces by capacity and audience behavior. Do not schedule every channel. Pick the few the team can maintain.
Define recurring slots:
Each slot needs input source, owner, format, CTA, and reuse path.
Distribution thesis:
[why this audience will keep paying attention]
Source routes:
| Source material | Route | Surface | Format | Owner | CTA |
This week:
1. [post/story]
2. [post/story]
3. [post/story]
Reuse map:
- [source] -> [formats]
Collection habits:
- [what to capture weekly]
Queue health:
- Starved source:
- Overused format:
- Channel at capacity:
Do not do:
- [channel or format to skip]