zhongwei/gh-gtmagents-gtm-agents-plugins-content-pipeline-orchestration
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-29 18:30:05 +08:00
commit b23f9bd0c6
12 changed files with 423 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
commands/distribute-assets.md Normal file
View File

@@ -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-<timestamp>.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.
---

48
commands/manage-production.md Normal file
View File

@@ -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-<timestamp>.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.
---

48
commands/plan-pillar.md Normal file
View File

@@ -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-<timestamp>.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.
---