Post Packager
Turn drafts into a clean handoff package. Every post should be ready to approve, revise, or schedule without hunting for context.
Inputs
- drafts or post ideas
- platforms
- planned dates and times
- assets
- CTA
- approval owner
- campaign or pillar
- claims requiring review
Workflow
Normalize each post:
platform, copy, scheduled time, asset, CTA, status, and owner.
Validate platform fit:
length, formatting, tone, media assumptions, and CTA intensity.
Flag risks:
unsupported claims, missing visuals, duplicate copy, sensitive wording, or weak hooks.
Add approval status:
ready, needs edit, needs asset, needs legal/fact check, or blocked.
Produce final package:
table first, then post-by-post copy blocks.
Taste Rules
- Do not silently rewrite approved copy unless asked.
- Keep review notes concrete and actionable.
- Separate missing assets from copy problems.
- Preserve platform-native formatting.
- Make the package easy to paste into scheduling tools or agent workflows.
Output Format
## Scheduling Package
| ID | Date | Time | Platform | Status | Asset | CTA | Review Note |
| --- | --- | --- | --- | --- | --- | --- | --- |
## Final Copy
### [ID] [Platform]
[copy]
## Blockers
- [missing input or risk]
AgentReacher Notes
Use this as the final step before AgentReacher schedules posts. It turns strategy, drafts, and calendar slots into a reviewable queue.
Example usage in AgentReacher: "Package these 18 campaign posts for scheduling next month and flag anything that needs approval."
1---2name: post-packager3description: Convert social media drafts into an approval-ready scheduling package with platform, copy, timing, assets, CTA, and review notes. Use when preparing posts for scheduling, review, or handoff.4---56# Post Packager78Turn drafts into a clean handoff package. Every post should be ready to approve, revise, or schedule without hunting for context.910## Inputs1112- drafts or post ideas13- platforms14- planned dates and times15- assets16- CTA17- approval owner18- campaign or pillar19- claims requiring review2021## Workflow22231. Normalize each post:24 platform, copy, scheduled time, asset, CTA, status, and owner.25262. Validate platform fit:27 length, formatting, tone, media assumptions, and CTA intensity.28293. Flag risks:30 unsupported claims, missing visuals, duplicate copy, sensitive wording, or weak hooks.31324. Add approval status:33 ready, needs edit, needs asset, needs legal/fact check, or blocked.34355. Produce final package:36 table first, then post-by-post copy blocks.3738## Taste Rules3940- Do not silently rewrite approved copy unless asked.41- Keep review notes concrete and actionable.42- Separate missing assets from copy problems.43- Preserve platform-native formatting.44- Make the package easy to paste into scheduling tools or agent workflows.4546## Output Format4748```md49## Scheduling Package50| ID | Date | Time | Platform | Status | Asset | CTA | Review Note |51| --- | --- | --- | --- | --- | --- | --- | --- |5253## Final Copy54### [ID] [Platform]55[copy]5657## Blockers58- [missing input or risk]59```6061## AgentReacher Notes6263Use this as the final step before AgentReacher schedules posts. It turns strategy, drafts, and calendar slots into a reviewable queue.6465Example usage in AgentReacher: "Package these 18 campaign posts for scheduling next month and flag anything that needs approval."