commit b23f9bd0c61dedef1c0ebf1c241f0663ed8c4c2a Author: Zhongwei Li Date: Sat Nov 29 18:30:05 2025 +0800 Initial commit diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json new file mode 100644 index 0000000..ca24cb1 --- /dev/null +++ b/.claude-plugin/plugin.json @@ -0,0 +1,24 @@ +{ + "name": "content-pipeline-orchestration", + "description": "Content pillar orchestration from planning through production and distribution", + "version": "1.0.0", + "author": { + "name": "GTM Agents", + "email": "opensource@intentgpt.ai" + }, + "skills": [ + "./skills/editorial-calendar/SKILL.md", + "./skills/asset-tracking/SKILL.md", + "./skills/distribution-checklist/SKILL.md" + ], + "agents": [ + "./agents/editorial-director.md", + "./agents/creative-producer.md", + "./agents/distribution-lead.md" + ], + "commands": [ + "./commands/plan-pillar.md", + "./commands/manage-production.md", + "./commands/distribute-assets.md" + ] +} \ No newline at end of file diff --git a/README.md b/README.md new file mode 100644 index 0000000..0f32033 --- /dev/null +++ b/README.md @@ -0,0 +1,3 @@ +# content-pipeline-orchestration + +Content pillar orchestration from planning through production and distribution diff --git a/agents/creative-producer.md b/agents/creative-producer.md new file mode 100644 index 0000000..e4f6ddb --- /dev/null +++ b/agents/creative-producer.md @@ -0,0 +1,27 @@ +--- +name: creative-producer +description: Oversees content production workflow from briefs through design, copy, and approvals. +model: haiku +--- + +# Creative Producer Agent + +## Responsibilities +- Turn editorial briefs into production-ready tasks with milestones and review checkpoints. +- Coordinate writers, designers, video/audio partners, and localization teams. +- Track asset status, feedback cycles, and version control. +- Ensure accessibility, brand, and legal requirements are met before delivery. + +## Process +1. **Brief Intake** – confirm scope, goals, target channels, asset specs. +2. **Production Plan** – define tasks, owners, tooling (Figma, Docs, CMS), and deadlines. +3. **Feedback Management** – schedule reviews, consolidate comments, resolve blockers. +4. **Quality & Compliance** – run QA checklists (links, voice, accessibility, localization). +5. **Handoff** – package final assets with metadata, thumbnails, transcripts, and publishing notes. + +## Outputs +- Production tracker (asset, status, owner, next action, due date). +- Feedback/resolution log. +- Delivery checklist per asset. + +--- diff --git a/agents/distribution-lead.md b/agents/distribution-lead.md new file mode 100644 index 0000000..231c4dd --- /dev/null +++ b/agents/distribution-lead.md @@ -0,0 +1,27 @@ +--- +name: distribution-lead +description: Plans and executes multi-channel distribution, amplification, and measurement for content pillars. +model: haiku +--- + +# Distribution Lead Agent + +## Responsibilities +- Build launch + evergreen distribution plans (owned, earned, paid, partner channels). +- Manage publishing workflows (CMS, social schedulers, newsletters, enablement hubs). +- Coordinate with paid, social, PR, partner teams for amplification. +- Track performance, feedback, and recycling opportunities. + +## Process +1. **Asset Intake** – gather final assets, metadata, CTAs, localization requirements. +2. **Channel Planning** – map where/when assets will run, including repurposed formats. +3. **Publishing Execution** – schedule posts, emails, syndication, partner drops, and internal enablement. +4. **Promotion Layer** – align paid boosts, influencer/partner collaborations, ABM tie-ins. +5. **Performance Review** – monitor KPIs, capture learnings, recommend optimizations or refresh. + +## Outputs +- Distribution calendar with channels, owners, UTMs, and status. +- Amplification checklist (partners, paid boosts, internal comms). +- Performance summary report (per asset + overall pillar). + +--- diff --git a/agents/editorial-director.md b/agents/editorial-director.md new file mode 100644 index 0000000..c002a44 --- /dev/null +++ b/agents/editorial-director.md @@ -0,0 +1,29 @@ +--- +name: editorial-director +description: Owns content pillar strategy, calendars, and cross-functional alignment + for major programs. +model: haiku +--- + + +# Editorial Director Agent + +## Responsibilities +- Translate business objectives into pillar themes, hero assets, and derivative content roadmap. +- Coordinate stakeholders (PMM, design, legal, executives) for approvals and messaging consistency. +- Maintain editorial calendar, briefing templates, and backlog grooming. +- Manage quarterly retros, performance insights, and experimentation roadmap. + +## Workflow +1. **Brief Synthesis** – gather goals, personas, channel mix, asset formats. +2. **Pillar Planning** – outline hero assets, supporting pieces, and distribution plan. +3. **Calendar Management** – assign owners, deadlines, and review checkpoints. +4. **Governance** – enforce voice/tone, brand, compliance, accessibility requirements. +5. **Measurement Loop** – review performance data to prioritize optimizations. + +## Outputs +- Editorial calendar (dates, assets, owners, status, dependencies). +- Creative brief templates per asset. +- Retro + experiment tracker for future cycles. + +--- diff --git a/commands/distribute-assets.md b/commands/distribute-assets.md new file mode 100644 index 0000000..8f119a2 --- /dev/null +++ b/commands/distribute-assets.md @@ -0,0 +1,48 @@ +--- +name: distribute-assets +description: Creates a distribution + amplification plan with schedule, UTMs, and partner alignment. +usage: /content-pipeline-orchestration:distribute-assets --pillar "AI readiness" --channels "blog,email,linkedin" --partners "Acme" +--- + +# Command: distribute-assets + +## Inputs +- **pillar** – content pillar or campaign name. +- **channels** – comma-separated list (blog, CMS, email, social, paid, partner, enablement). +- **partners** – optional partner/community co-marketing list. +- **utm** – optional base UTM template. +- **boosts** – optional paid boost budget or parameters. + +### GTM Agents Pattern & Plan Checklist +> Mirrors GTM Agents orchestrator guidance @puerto/plugins/orchestrator/README.md#112-325. + +- **Pattern selection**: Default to **pipeline** (mapping → prep → amplification → measurement → feedback). If channel prep + amplification can run in parallel, log a **diamond** with merge gate. +- **Plan schema**: Save `.claude/plans/plan-.json` capturing objective, stages, task IDs, channel groupings, context passing (UTMs, assets), guardrails, and success metrics (engagement, pipeline, partner reach). +- **Tool hooks**: Reference `docs/gtm-essentials.md` stack (Serena for CMS/pixel patches, Context7 for platform docs, Sequential Thinking for retro cadence, Playwright for landing/social QA). +- **Guardrails**: Set retry limit (default 2) for failed publishes; escalation ladder = Distribution Lead → Editorial Director → Marketing Director. +- **Review**: Use `docs/usage-guide.md#orchestration-best-practices-puerto-parity` checklist before execution to confirm agents, dependencies, deliverables. + +## Workflow +1. **Channel Mapping** – assign assets to channels with timing, CTA, and owner. +2. **Publishing Prep** – outline CMS/social scheduler steps, asset variants, localization, and approvals. +3. **Amplification Plan** – coordinate paid boosts, influencer/partner drops, internal comms, enablement uploads. +4. **Measurement Hooks** – define UTMs, dashboards, alerting, and reporting cadence. +5. **Feedback & Recycling** – schedule retro checkpoints and repurposing opportunities. + +## Outputs +- Distribution calendar with timestamps, channels, owners, UTMs, and status. +- Amplification checklist (partners, paid, internal enablement, ABM tie-ins). +- Measurement + feedback plan. +- Plan JSON entry stored/updated in `.claude/plans` for audit trail. + +## Agent/Skill Invocations +- `distribution-lead` – drives publishing + amplification. +- `distribution-checklist` skill – ensures operational rigor per channel. +- `editorial-director` – confirms narrative alignment. + +## GTM Agents Safeguards +- **Fallback agents**: document substitutes (e.g., Editorial Director covering Distribution Lead) when specialists unavailable. +- **Escalation triggers**: if UTMs misfire, partner SLAs slip, or alert thresholds breach twice within 48h, trigger escalation to Content + Growth leadership per GTM Agents runbook. +- **Plan maintenance**: update plan JSON + change log whenever channels, partners, or measurement hooks change to maintain GTM Agents-grade auditability. + +--- diff --git a/commands/manage-production.md b/commands/manage-production.md new file mode 100644 index 0000000..18cb639 --- /dev/null +++ b/commands/manage-production.md @@ -0,0 +1,48 @@ +--- +name: manage-production +description: Generates a production tracker with tasks, owners, feedback cycles, and QA steps. +usage: /content-pipeline-orchestration:manage-production --pillar "AI readiness" --assets "ebook,video,design kit" +--- + +# Command: manage-production + +## Inputs +- **pillar** – reference pillar or campaign. +- **assets** – comma-separated asset types or names. +- **tools** – optional tools/platforms (Docs, Figma, Notion, CMS). +- **qa** – include QA/evidence plan (default true). +- **localization** – regions/languages requiring localization. + +### GTM Agents Pattern & Plan Checklist +> Pulled from GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. + +- **Pattern selection**: Production typically runs **pipeline** (tasks → owners → feedback → QA → packaging). Use **diamond** when localization or QA evidence can run parallel; document choice in the plan header. +- **Plan schema**: Save or update `.claude/plans/plan-.json` with task IDs, asset references, tooling context, parallel groups, handoff requirements, error handling, and success criteria (on-time %, defect ceiling). +- **Tool hooks**: Reference `docs/gtm-essentials.md` stack (Serena for CMS automation patches, Context7 for brand/legal standards, Sequential Thinking for retros, Playwright for accessibility/QA screens). +- **Guardrails**: Default retry limit = 2 for failed QA; escalation ladder = Creative Producer → Editorial Director → Marketing Director. +- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm agents, dependencies, deliverables. + +## Workflow +1. **Task Breakdown** – create tasks per asset (draft, design, review, localization, QA). +2. **Owner Assignment** – map writers, designers, reviewers, approvers, and due dates. +3. **Feedback Loops** – schedule review checkpoints, consolidate feedback instructions. +4. **QA Checklist** – ensure brand, accessibility, legal, and technical requirements are validated. +5. **Asset Packaging** – outline final delivery steps (naming conventions, metadata, storage paths). + +## Outputs +- Production tracker (task, owner, status, due date, dependencies, comments). +- QA/evidence log template. +- Asset handoff checklist with storage locations. +- Plan JSON entry stored/updated in `.claude/plans` for audit trail. + +## Agent/Skill Invocations +- `creative-producer` – runs production board + QA. +- `asset-tracking` skill – ensures dependencies + metadata. +- `distribution-lead` – receives handoff package for publishing. + +## GTM Agents Safeguards +- **Fallback agents**: document substitutes (e.g., Editorial Director covering Creative Producer) when specialists unavailable. +- **Escalation triggers**: if QA defects, brand issues, or missed deadlines breach guardrails twice in 48h, escalate to Content + Growth leadership per GTM Agents runbook. +- **Plan maintenance**: update plan JSON and change log whenever assets, owners, or QA scope shift so audit trail mirrors GTM Agents standards. + +--- diff --git a/commands/plan-pillar.md b/commands/plan-pillar.md new file mode 100644 index 0000000..040d082 --- /dev/null +++ b/commands/plan-pillar.md @@ -0,0 +1,48 @@ +--- +name: plan-pillar +description: Produces a content pillar blueprint with hero assets, derivatives, and distribution plan. +usage: /content-pipeline-orchestration:plan-pillar --theme "AI readiness" --window 8w --channels "blog,video,webinar" +--- + +# Command: plan-pillar + +## Inputs +- **theme** – content pillar topic. +- **window** – program duration. +- **channels** – comma-separated roster (blog, video, webinar, social, email, enablement). +- **audiences** – optional persona/vertical list. +- **goals** – optional KPIs (pipeline, subscribers, product adoption). + +### GTM Agents Pattern & Plan Checklist +> Derived from GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. + +- **Pattern selection**: Default to **pipeline** (brief → hero asset → derivatives → owners → distribution). Use **diamond** when creative pods and distribution prep can run in parallel; document the pattern in the plan header. +- **Plan schema**: Save `.claude/plans/plan-.json` with objective, asset stages, task IDs, parallel groups, dependency graph, error handling, and success criteria (e.g., MQL, pipeline, share of voice). +- **Tool hooks**: Reference `docs/gtm-essentials.md` stack (Serena for CMS/landing updates, Context7 for brand/legal docs, Sequential Thinking for retros, Playwright for QA of landing pages). +- **Guardrails**: Define retry strategy (default 2) and escalation ladder (Editorial Director → Creative Producer → Marketing Director) for missed approvals or QA issues. +- **Review**: Before execution, run the checklist in `docs/usage-guide.md#orchestration-best-practices-puerto-parity` to confirm agents, dependencies, deliverables. + +## Workflow +1. **Brief Intake** – align on objectives, persona needs, proof assets, campaign tie-ins. +2. **Hero Asset Definition** – define flagship deliverables (ebook, webinar, video series) with requirements. +3. **Derivative Mapping** – outline derivative assets per channel with rough cadence. +4. **Resourcing & Owners** – assign writers, designers, reviewers, budgets, tooling. +5. **Distribution Hooks** – highlight promotion partners, paid support, enablement ties. + +## Outputs +- Pillar blueprint table (asset, format, owner, due date, CTA, dependency). +- Creative brief package template per asset. +- Initial distribution + amplification notes. +- Plan JSON entry stored/updated in `.claude/plans` for audit trail. + +## Agent/Skill Invocations +- `editorial-director` – leads strategy + calendar. +- `editorial-calendar` skill – enforces cadence + governance. +- `asset-tracking` skill – maps resources + dependencies. + +## GTM Agents Safeguards +- **Fallback agents**: document substitutes (e.g., Creative Producer covering Distribution Lead) when specialists unavailable. +- **Escalation triggers**: if asset delivery or channel guardrails (cadence, QA defects) breach twice within 48h, trigger escalation to Content + Growth leadership per GTM Agents playbook. +- **Plan maintenance**: Every scope change (asset count, owner, channel) must update the plan JSON and change log to maintain parity with GTM Agents audits. + +--- diff --git a/plugin.lock.json b/plugin.lock.json new file mode 100644 index 0000000..6a2f203 --- /dev/null +++ b/plugin.lock.json @@ -0,0 +1,77 @@ +{ + "$schema": "internal://schemas/plugin.lock.v1.json", + "pluginId": "gh:gtmagents/gtm-agents:plugins/content-pipeline-orchestration", + "normalized": { + "repo": null, + "ref": "refs/tags/v20251128.0", + "commit": "035d1c6db9112c6fe112bcf5ccc1ea3b5c6ee3f7", + "treeHash": "7870f800f98910d75c08386404a27e315606c675d862c5f721bcd1d042fe9d0a", + "generatedAt": "2025-11-28T10:17:11.438114Z", + "toolVersion": "publish_plugins.py@0.2.0" + }, + "origin": { + "remote": "git@github.com:zhongweili/42plugin-data.git", + "branch": "master", + "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390", + "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data" + }, + "manifest": { + "name": "content-pipeline-orchestration", + "description": "Content pillar orchestration from planning through production and distribution", + "version": "1.0.0" + }, + "content": { + "files": [ + { + "path": "README.md", + "sha256": "0bb9f936371e25edd717d693bb15e8469277c980014da396566a45cc376c185a" + }, + { + "path": "agents/editorial-director.md", + "sha256": "bf1dc71d4be709ddef331380a5fb85a6e252dbd42493e67297bcad6bc7a728be" + }, + { + "path": "agents/creative-producer.md", + "sha256": "0ff483701c70997d965f6903fde587ca405f14cebad7fe1bd71954c392f96424" + }, + { + "path": "agents/distribution-lead.md", + "sha256": "9c907d3d3e125b1f8c1e6f6a620b817637516efba5b330a8fddf001a4ac77771" + }, + { + "path": ".claude-plugin/plugin.json", + "sha256": "5fbc9aa74a59ab98ad08406b616b1efc93e5ec492f2c427426b4edc5b988b5f3" + }, + { + "path": "commands/plan-pillar.md", + "sha256": "de059cb48f11ebbab0b20d716e361f073cb6bb642018f6ef95ce256028f54dd6" + }, + { + "path": "commands/distribute-assets.md", + "sha256": "7bbd1af8b94c69ca054f0a19d7f040667058261f99d0b9a6ed268e26dd9517ed" + }, + { + "path": "commands/manage-production.md", + "sha256": "7532516682ceacff762849583484db1e74ae742f026fd790a3814ce301988713" + }, + { + "path": "skills/asset-tracking/SKILL.md", + "sha256": "b3a2a42f37c1827fee36a318e3bf77cf8b5d026bfe70eee11edbba16e744a79a" + }, + { + "path": "skills/distribution-checklist/SKILL.md", + "sha256": "f2aa4721d25ebb06b32af0c159ded3bbe548c9f169cb02087ac8c52baadd2371" + }, + { + "path": "skills/editorial-calendar/SKILL.md", + "sha256": "f349f7da3bd42e48d229f7422ac3fd82800434b1cbefb5503ef7a02dc34c6ae2" + } + ], + "dirSha256": "7870f800f98910d75c08386404a27e315606c675d862c5f721bcd1d042fe9d0a" + }, + "security": { + "scannedAt": null, + "scannerVersion": null, + "flags": [] + } +} \ No newline at end of file diff --git a/skills/asset-tracking/SKILL.md b/skills/asset-tracking/SKILL.md new file mode 100644 index 0000000..3536a7b --- /dev/null +++ b/skills/asset-tracking/SKILL.md @@ -0,0 +1,31 @@ +--- +name: asset-tracking +description: Use when managing asset metadata, dependencies, and delivery workflows + across teams. +--- + +# Content Asset Tracking Skill + +## When to Use +- Coordinating production across writers, designers, video editors, and localization teams. +- Tracking asset dependencies (illustrations, data pulls, interviews) and approvals. +- Preparing handoffs to distribution, enablement, or partner teams. + +## Framework +1. **Metadata Schema** – asset ID, pillar, audience, stage, CTA, owner, status, storage link. +2. **Dependency Mapping** – highlight required inputs (stats, quotes, screenshots, product access). +3. **Version Control** – naming conventions, change history, approval timestamps. +4. **Delivery Checklist** – thumbnails, transcripts/captions, localization files, CMS fields. +5. **Analytics Hooks** – UTMs, tracking parameters, reporting sheet references. + +## Templates +- Asset tracker spreadsheet/board view. +- Dependency checklist (input, owner, due date, status). +- Delivery package template for distribution + enablement teams. + +## Tips +- Centralize assets in shared drives or DAM with consistent naming. +- Automate reminders when dependencies slip or approvals are overdue. +- Tie tracker to distribution calendar to visualize readiness. + +--- diff --git a/skills/distribution-checklist/SKILL.md b/skills/distribution-checklist/SKILL.md new file mode 100644 index 0000000..04c256a --- /dev/null +++ b/skills/distribution-checklist/SKILL.md @@ -0,0 +1,31 @@ +--- +name: distribution-checklist +description: Use when planning multi-channel publishing, promotions, and measurement + for content pillars. +--- + +# Distribution & Amplification Checklist Skill + +## When to Use +- Launching new hero assets or campaigns across multiple channels. +- Coordinating owned, earned, and paid amplification efforts. +- Auditing distribution readiness before go-live. + +## Framework +1. **Channel Readiness** – confirm CMS/social/email templates, personalization, localization plans. +2. **Publishing Steps** – detail scheduling, approvals, assets (thumbnails, snippets, UTMs). +3. **Amplification** – partner drops, paid boosts, influencer outreach, employee advocacy, enablement kits. +4. **Measurement** – define KPIs, UTMs, dashboards, alerting thresholds, reporting cadence. +5. **Feedback & Recycling** – plan check-ins for performance review, comments, repurposing opportunities. + +## Templates +- Distribution checklist per channel (tasks, owner, due date, status). +- Amplification matrix (partner, asset, CTA, logistics). +- Reporting sheet linking metrics to assets/UTMs. + +## Tips +- Align UTMs + naming conventions before scheduling to keep analytics clean. +- Document embargoes and partner requirements to avoid misfires. +- Schedule follow-up touchpoints to convert top performers into evergreen assets. + +--- diff --git a/skills/editorial-calendar/SKILL.md b/skills/editorial-calendar/SKILL.md new file mode 100644 index 0000000..599d963 --- /dev/null +++ b/skills/editorial-calendar/SKILL.md @@ -0,0 +1,30 @@ +--- +name: editorial-calendar +description: Use when structuring pillar calendars, approvals, and cadence governance. +--- + +# Editorial Calendar Systems Skill + +## When to Use +- Planning multi-asset campaigns or pillar programs. +- Coordinating cross-functional review cycles. +- Auditing content backlog, status, and alignment to GTM themes. + +## Framework +1. **Cadence** – map publish dates, lead times, and dependencies. +2. **Ownership** – assign writers, reviewers, approvers, localization partners. +3. **Workflow Stages** – draft → review → design → legal → ready → scheduled → live. +4. **Metadata** – persona, stage, CTA, channels, asset type, pillar tag. +5. **Governance** – color-coding, status thresholds, reminder automation. + +## Templates +- Calendar view (by week) with status tags. +- Intake brief + approval checklist. +- Monday/Asana/Notion board schema for pipeline tracking. + +## Tips +- Keep a backlog column for ideas; groom weekly. +- Automate reminders for approvals to shorten cycle time. +- Document freeze windows (holidays, launches) to avoid conflicts. + +---