Campaign Calendar

Generate a rolling campaign calendar by scanning knowledge-base/marketing/distribution-content/*.md files and grouping them by status. Replaces the fixed distribution plan that expires with no rollover.

Arguments

$ARGUMENTS is parsed for optional flags:

campaign-calendar [--headless]

If $ARGUMENTS contains --headless, set HEADLESS=true. This skill has no interactive prompts, so --headless is a no-op for convention compliance.

Execution

Phase 1: Scan Content Files

1. Glob knowledge-base/marketing/distribution-content/*.md to find all content files.

2. If zero files are found, write a calendar with the empty state message (see Phase 3) and skip to Phase 4.

3. For each file found, read the file and extract YAML frontmatter fields:

   • title (string)
   • type (string: case-study, pillar, announcement)
   • publish_date (YYYY-MM-DD)
   • channels (comma-separated string)
   • status (draft, scheduled, published)

4. If a file has no YAML frontmatter delimiters (---), skip it and note: "Skipped [filename]: no frontmatter found."

5. If a file has frontmatter but is missing required fields (title, status), include it with "unknown" for missing values.

Phase 2: Classify Entries

Classify each content file into one of four groups using status and publish_date:

Group	Condition	Sort Order
Overdue	status: scheduled AND publish_date < today	Oldest first (most overdue at top)
Upcoming	status: scheduled AND publish_date >= today	Soonest first
Draft	status: draft	Alphabetical by title
Published	status: published	Most recent publish_date first

Today's date: use the current date at execution time.

Phase 3: Generate Calendar Markdown

Write the calendar to knowledge-base/marketing/campaign-calendar.md with this structure:

---
last_updated: YYYY-MM-DD
---

# Campaign Calendar

Rolling view of content distributions. Auto-generated from `distribution-content/` frontmatter.

## Overdue

> These items have a scheduled publish date in the past but have not been published.

| Title | Type | Publish Date | Channels | Status |
|-------|------|-------------|----------|--------|
| ... | ... | ... | ... | scheduled |

## Upcoming

| Title | Type | Publish Date | Channels | Status |
|-------|------|-------------|----------|--------|
| ... | ... | ... | ... | scheduled |

## Draft

| Title | Type | Publish Date | Channels | Status |
|-------|------|-------------|----------|--------|
| ... | ... | ... | ... | draft |

## Published

| Title | Type | Publish Date | Channels | Status |
|-------|------|-------------|----------|--------|
| ... | ... | ... | ... | published |

Rules:

• Omit any section that has zero entries (do not show empty tables).
• If zero files were found in Phase 1, write: No content files found in distribution-content/.
• The last_updated frontmatter field uses today's date in YYYY-MM-DD format.
• If the Overdue section has entries, add a blockquote warning above its table.

Phase 4: Write and Report

1. Write the generated markdown to knowledge-base/marketing/campaign-calendar.md.

2. If running in CI (detected by the presence of GITHUB_ACTIONS environment variable or if the workflow prompt includes commit instructions):

   Run these commands to persist the calendar:

   git add knowledge-base/marketing/campaign-calendar.md
   git diff --cached --quiet && echo "Calendar unchanged, skipping commit." && exit 0
   git commit -m "ci: update campaign calendar [skip ci]"
   git push origin main || { git pull --rebase origin main && git push origin main; }
   

3. If running manually (no CI environment detected):

   Print: "Calendar written to knowledge-base/marketing/campaign-calendar.md. To persist, run: gh workflow run scheduled-campaign-calendar.yml"