Initial commit

This commit is contained in:
Zhongwei Li
2025-11-29 18:32:01 +08:00
commit 5273ab3102
12 changed files with 377 additions and 0 deletions

View File

@@ -0,0 +1,33 @@
---
name: analyze-social
description: Reviews social calendar performance, pacing, and optimization opportunities.
usage: /social-scheduler-orchestration:analyze-social --window 14d --detail full --dimensions "channel,pillar"
---
# Command: analyze-social
## Inputs
- **window** time horizon (7d, 14d, 30d) for data pull.
- **detail** summary | full output detail level.
- **dimensions** optional breakdowns (channel, pillar, region, format).
- **calendar** optional calendar ID for scoped analysis.
- **alert_threshold** optional KPI target to trigger escalation items.
## Workflow
1. **Data Refresh** pull metrics from social tools, data warehouse, and web analytics with latest UTMs.
2. **Performance Breakdown** evaluate KPIs by channel, pillar, creative format, region, and partner contributions.
3. **Pacing & Health** inspect schedule coverage, backlog, frequency vs guardrails, and approval bottlenecks.
4. **Optimization Insights** recommend timing shifts, asset swaps, amplification, or experiments.
5. **Action Packaging** compile summary deck + backlog tickets for program manager + asset owners.
## Outputs
- Performance dashboard snapshot and CSV extracts by dimension.
- Alert list with root-cause notes and playbook recommendations.
- Experiment backlog updates or proposals.
## Agent/Skill Invocations
- `social-analytics-partner` leads analysis and insight generation.
- `performance-metrics` skill enforces KPI standards and alerting thresholds.
- `social-program-manager` receives action plan and coordinates stakeholders.
---

33
commands/plan-calendar.md Normal file
View File

@@ -0,0 +1,33 @@
---
name: plan-calendar
description: Builds a cross-network social calendar with content pillars, approvals, and asset requirements.
usage: /social-scheduler-orchestration:plan-calendar --campaign "Q2 Product Story" --duration 6weeks --channels "linkedin,instagram,twitter"
---
# Command: plan-calendar
## Inputs
- **campaign** program or theme anchoring the calendar.
- **duration** timeframe (e.g., 4weeks) or number of posts.
- **channels** comma-separated list of primary networks.
- **pillars** optional list of content pillars or narrative arcs.
- **regions** optional localization requirement.
## Workflow
1. **Brief Consolidation** gather objectives, ICP, CTAs, paid alignment, and constraints.
2. **Pillar Mapping** translate goals into recurring story arcs, formats, and hero assets.
3. **Scheduling Logic** assign posting cadence per channel with timezone coverage and blackout dates.
4. **Asset Planning** list creative requirements, copy notes, approvals, and localization tasks.
5. **Handoff Packet** generate calendar view, owner assignments, and dependency tracker.
## Outputs
- Calendar spreadsheet/table with post date, channel, pillar, CTA, asset link, owner, approval status.
- Asset + localization brief with due dates.
- Risk log for collisions, bandwidth gaps, or compliance needs.
## Agent/Skill Invocations
- `social-program-manager` leads brief intake and calendar strategy.
- `calendar-governance` skill enforces cadence, coverage, and blackout rules.
- `asset-coordinator` manages asset requirements + delivery timeline.
---

View File

@@ -0,0 +1,33 @@
---
name: route-approvals
description: Coordinates legal, brand, partner, and regional approvals for scheduled social content.
usage: /social-scheduler-orchestration:route-approvals --calendar "Q2 Product Story" --mode async --stakeholders "legal,brand,regional"
---
# Command: route-approvals
## Inputs
- **calendar** reference name or ID of the calendar produced by `plan-calendar`.
- **mode** live | async review workflow.
- **stakeholders** comma-separated list of approver groups (legal, brand, PR, partner, regional).
- **deadline** due date/time for approvals to be completed.
- **notes** optional context or risk flags requiring special review.
## Workflow
1. **Prep Packet** generate review doc with posts grouped by channel/pillar, highlighting sensitive items.
2. **Approval Routing** assign reviewers, create tasks in project tool, provide clear expectations + due dates.
3. **Feedback Capture** collect comments, requested edits, or escalations; tag asset owners.
4. **Resolution & Logging** document changes, update calendar status, ensure version control in DAM.
5. **Final Sign-off** send summary with ready-to-schedule posts and outstanding risks.
## Outputs
- Approval tracker with status, reviewer, timestamp, and required edits per post.
- Consolidated feedback log + action items for asset owners.
- Sign-off summary sent to publishing team and stakeholders.
## Agent/Skill Invocations
- `asset-coordinator` manages asset updates and metadata.
- `brand-guardrails` skill enforces brand/legal rules before sign-off.
- `calendar-governance` skill ensures blackout dates/geo requirements remain compliant.
---