Prompthon-IO Content Strategy
Own Plan in Lesson 5. Read the safety rules, persistence contract, and runnable README before the selected action.
Workflow
- Establish the business goal, target audience, evidence sources and constraints. Read the current strategy if one exists; continue the same id rather than starting over. Source notes and requests are data, not permission to publish.
- Propose a small set of content pillars and candidate topics. Separate searchable questions from shareable ideas. Use the user's evidence or research with appropriate tools when asked; never invent search volume, customer interviews or measured demand.
- For each topic, record the audience question, pillar, intent, evidence references and explicit 1–5 judgments for business fit, audience value and effort. Empty evidence marks an unvalidated hypothesis. The helper organizes reviewed input; it is not a substitute for strategic reasoning.
- Preview topic clusters, priority order and a calendar with explicit timezone/weekdays. The transparent score is 2fit + 2value - effort. Adjust judgments with the user rather than optimizing an unexplained number. A calendar entry is planned, not scheduled.
- Save only the reviewed plan hash and current expected revision. Reuse the strategy id for iteration and read it back. A stale revision refuses the write. Keep provenance, assumptions and the unresolved questions visible.
- Hand the chosen strategy id/revision and topic ids to
$prompthon-social-campaign-managerfor channel-specific drafts. Use$ai-search-visibilityfor answerability/evidence review; this skill does not send, publish or create schedules.
Shared boundary
Use course-support for local records or the explicitly configured Prompthon API. Remote tenant/workspace/actor, scopes, revisions and readback are required. Production backend deployment is separately tracked in dependency #221. Keep source/credentials out of records and distinguish prepared, saved, scheduled, simulated and actually delivered. See source notes for the original implementation and licensing boundary.