home / skills / gtmagents / gtm-agents / editorial-calendar

editorial-calendar skill

safe

/plugins/content-pipeline-orchestration/skills/editorial-calendar

This skill helps you structure pillar calendars, coordinate approvals, and govern cadence to accelerate content campaigns.

npx playbooks add skill gtmagents/gtm-agents --skill editorial-calendar

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.1 KB

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

---

Overview

This skill helps teams design and maintain a production-ready editorial calendar for pillar programs, multi-asset campaigns, and cadence governance. It bundles a practical framework for cadence, ownership, workflow stages, metadata and governance so you can reduce bottlenecks and keep content aligned to GTM themes. Use it to standardize approvals, intake, and scheduling across marketing, sales enablement, and localization.

How this skill works

The skill inspects your calendar needs and produces a repeatable schema: publish cadence with lead times and dependencies, clear role assignments for writers/reviewers/approvers, and a staged workflow from draft through live. It outputs templates for calendar views, intake briefs, and approval checklists and recommends automation points for reminders and status thresholds. You get a governance layer with color-coding and freeze-window policies to prevent conflicts around launches and holidays.

When to use it

Planning multi-asset campaigns or long-form pillar content programs
Coordinating cross-functional review and legal/design approval cycles
Auditing backlog, content status, and alignment to GTM themes
Setting publishing cadence and lead times for recurring series
Onboarding teams to a consistent intake and approval workflow

Best practices

Map publish dates and upstream dependencies early to expose bottlenecks
Assign clear owners for writing, review, approval, and localization
Define workflow stages (draft → review → design → legal → ready → scheduled → live)
Standardize metadata (persona, funnel stage, CTA, channel, pillar tag) for discoverability
Automate reminders for approvals and maintain a documented freeze-window calendar

Example use cases

Create a weekly calendar view with status tags for a pillar content program
Design an intake brief plus approval checklist for gated asset launches
Set up a Monday/Asana/Notion board schema to track content pipeline and handoffs
Audit and prioritize a backlog against quarterly GTM themes
Implement reminder automation to shorten review cycle times before a product launch

FAQ

Can this skill work with existing PM or wiki tools?

Yes. It provides board schemas and templates that map to common tools like Asana, Monday, and Notion so you can adopt the framework without rebuilding systems.

How does it prevent schedule conflicts around major launches?

It enforces documented freeze windows and status thresholds and recommends color-coded calendar rules and automated reminders so critical dates are protected.