content

name	content
description	Weekly content production pipeline. Plans calendar, writes content across channels, specs visual assets, handles scheduling. Runs Monday through Friday. Octopus colors: Green (content) + Red-Orange (design) + Blue (build) + Purple (coordination).

/content: Weekly Content Production

Octopus Colors: Green (Marketer) + Red-Orange (Designer) + Blue (Maker) + Purple (Manager)

Process

Monday: Planning (Purple)

1. Read .chairman/config.json and departments/marketing/knowledge/
2. Check current priorities, upcoming events, seasonal patterns
3. Draft weekly content calendar: what, where, when
4. Present calendar to Chairman for approval

Tuesday-Thursday: Production (Green + Red-Orange)

1. Write content per approved calendar
2. For each piece:
   • Green writes the copy (social posts, newsletter, blog, LinkedIn)
   • Red-Orange specs any visual assets needed (dimensions, brand notes, layout description)
   • Match tone to platform (professional for LinkedIn, casual for social)
3. Present batch to Chairman for review

Friday: Scheduling (Blue)

1. Finalize approved content
2. Format for each platform
3. Prepare scheduling notes (post times, hashtags, links)

Output Format

# Content Calendar: Week of [Date]

## Monday
- [Platform]: [Topic] | Status: [draft/approved/scheduled]

## Tuesday
...

## Content Pieces

### [Title]
**Platform:** [where] | **Type:** [post/article/newsletter]
**Copy:**
[The actual content]

**Visual:** [Description of needed image/graphic, or "text only"]
**Approval:** [ ] Approve  [ ] Edit  [ ] Kill

Rules

• Maximum 1 piece per platform per day unless Chairman requests more
• If $ARGUMENTS provided, focus on that topic or content type
• Save approved content to departments/marketing/knowledge/content-log.md
• Never publish without Chairman approval (approval gate)