Input
Prioritize reading existing account descriptions, historical content, and data. Only confirm when missing and it would change the strategy:
- Domain, persona, and target audience.
- Business goals and priorities for this stage.
- Existing platforms, account stage, and historical performance.
- Update frequency, team size, and available time.
- Sustainable first-hand evidence and content sources.
- Business goals, brand boundaries, and content that cannot be made.
Can build an account profile from account-profile-template.md .
Method
1. Write a clear positioning promise
Use one sentence to explain "who, for whom, continuously provides what value, and why should they believe it." Positioning must be able to constrain topic selection; do not write vague slogans.
2. Map goals to content types
| Type | Main role | Common formats |
|---|---|---|
| Follower growth | Be discovered by new users | Tutorials, pitfalls, counterintuitive takes, trend explanations |
| Engagement | Activate existing audience | Questions, choices, controversies, shared experiences |
| Trust | Build professionalism and personality | Case studies, behind the scenes, retrospectives, in-depth methods |
| Conversion | Support products or services | Reviews, Q&A, case studies, collaborative content |
Do not apply a fixed ratio. Propose an initial ratio based on account stage, historical data, and capacity, and make clear that this is a hypothesis to be verified.
3. Build a topic pool
Each topic should record at least:
- Parent theme and one-sentence hook.
- Content goal and target audience.
- Primary platform and expandable platforms.
- First-hand evidence and evidence still missing.
- Timeliness window, priority, and estimated cost.
- Whether it belongs to a series.
Use topic-pool-template.md. Prioritize keeping topics that can be produced sustainably, reinforce positioning, and have real evidence.
4. Design series columns
Converge scattered topics into 2 to 4 columns. For each column, clearly write the content promise, evidence sources, suitable platforms, update frequency, and stopping conditions.
5. Generate a content calendar
Allocate capacity first, then schedule dates. Keep hot-topic slots and avoid locking in all future content. Set only one attributable experimental variable per cycle. Use content-calendar-template.md. Only create scheduling reminders when the user explicitly requests reminders and the current environment provides scheduling capability.
Output
Deliverables:
- One-sentence positioning.
- Stage goals and content mix hypothesis.
- 2 to 4 columns.
- Topic pool.
- Weekly or monthly calendar.
- Success metrics, stopping conditions, and the only experiment for this cycle.
If historical data is insufficient, explicitly write "establish a baseline" and do not fabricate precise targets.