icaire-comms-lead-plan-content
Plan ICAIRE content across website, newsletter, social, events, and partner channels. Use when the user asks for content pillars, a channel plan, calendar, audience, message angle, owner, or approval
SKILL.mdskills/icaire-comms-lead-plan-content/SKILL.md
GitHubICAIRE Comms Lead: Plan Content
Create a practical content plan that turns ICAIRE priorities, events, and updates into coordinated communications across channels.
Contract
- Start from the time horizon, audience, channels, objectives, and available source material.
- Use BigBrain or the ICAIRE MCP connector for ICAIRE initiatives, people, events, partner context, prior messaging, and open commitments when the user has not supplied enough source material.
- Turn scattered updates into content pillars, channel-specific angles, owners, deadlines, and approval steps.
- Match each content item to a real audience need or institutional objective.
- For planned visual assets, note that ICAIRE's primary brand color is
#4A9549and should be used as the main accent unless a campaign-specific approved design system overrides it. - Mark facts, assets, approvals, and source material needed before publication.
Workflow
- Define the planning frame.
- Identify planning period, channels, priority audiences, communications objective, publishing cadence, and constraints.
- If the user gives no channel list, consider website, newsletter, social, events, and partner channels, then include only the relevant ones.
- Gather source material.
- Read provided updates, calendars, reports, event notes, partner notes, and draft copy.
- Query BigBrain or ICAIRE MCP for current initiatives, events, stakeholders, and sensitivities when needed.
- Identify content pillars.
- Group potential content by theme, audience value, institutional priority, and proof points.
- Avoid turning every internal update into public content.
- Build the channel plan.
- Assign channel, format, message angle, audience, owner, draft date, publishing date, and approval path.
- Adapt the same story differently for different channels instead of duplicating copy.
- Flag dependencies.
- List facts to confirm, people to quote, assets to request, approvals to secure, and risks to manage.
- Review the plan.
- Check for audience balance, repetition, timing conflicts, sensitivity, and realistic production workload.
Output
Default to this structure unless the user requested another format:
Planning Frame: period, audiences, objectives, and channels.Content Pillars: priority themes and why they matter.Channel Plan: channel, format, angle, audience, owner, date, and approval.Calendar: recommended sequence or publishing schedule.Reuse Opportunities: how one story can become multiple assets.Dependencies: facts, assets, quotes, or approvals needed.Risks And Sensitivities: items needing careful handling.
Guardrails
- Do not invent events, owners, approvals, or publication dates.
- Do not plan public content from internal-only information without marking the approval need.
- Do not create a generic social calendar disconnected from ICAIRE priorities.
- Do not assume a channel is available or active unless the user or source material supports it.
- Do not ignore production capacity; keep the plan executable.