The mandate
Give each platform a job instead of copying one post everywhere.
Creates a platform-specific publishing, repurposing, engagement, and measurement system.
The Social Strategy Agent maps audience, format, source asset, hook, proof, CTA, timing, engagement ownership, and outcome measurement to a specific platform. Scheduling and publishing remain approval-gated external effects.
What to bring
Bring one audience, one priority channel, and source material worth adapting.
The plan needs to know what can be said, where the proof comes from, who can respond, and what a useful platform outcome looks like.
- 01
The brand, founder, product, or account whose social operation is being planned.
- 02
The first platform, selected for a specific audience and role.
- 03
The audience on this platform, including context and desired conversation.
- 04
Approved research, articles, product material, proof, spokespeople, and reusable source content.
- 05
The business outcome, audience response, and measurement horizon.
What you receive
A channel strategy, calendar, and response system built for context.
Every proposed post retains its source, approval state, platform logic, engagement owner, CTA, and outcome metric.
- 01
Social channel strategy
social/strategy.mdReady when
Audience, platform role, formats, proof, and stop conditions are explicit.
- 02
Approval-ready publishing calendar
social/calendar.jsonReady when
Each post has source material, owner, CTA, and approval state.
- 03
Engagement and escalation runbook
social/engagement.mdReady when
Response boundaries and sensitive-case escalation are defined.
The method
Assign the channel, adapt the source, and keep a human at the edge.
The workflow starts with the role of each platform and ends with monitored publishing and learning—not unattended distribution.
- 1
Assign
Give each selected platform a specific audience, role, format mix, and stop condition.
- 2
Adapt
Translate approved source assets into native hooks, proof, formats, CTAs, and timing.
- 3
Approve
Attach account scope, review status, engagement ownership, and escalation rules.
- 4
Learn
Review qualified visits, meaningful engagement, conversations, and future reuse.
Signals & guardrails
Automation must stop when context, sentiment, or authority changes.
Untraceable claims, copied platform strategy, sensitive replies without escalation, or publishing without account-scoped approval block execution.
Signs the work is useful
- Qualified visits from social
- Meaningful engagement rate
- Content-to-conversation conversion
Reasons to pause
- Automated publishing creates reputational harm
- Vanity metrics replace business outcomes
Approval boundary
External publishing
Technical appendix
The exact contract behind the profile.
Useful for operators who need to inspect the immutable Kit version, typed boundary, and verification surface.
- Kit
- company-suite@0.1.0
- Entrypoint
- plan-social-media
- Function
- plan-social-media
- Runtime
- python@3.12
- Input
- specialist-brief.schema.json
- Output
- specialist-plan.schema.json
Verification
specialist-plan-quality · specialist-plan-schema
Connected systems
Social publishing