| 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)
- Read
.chairman/config.json and departments/marketing/knowledge/
- Check current priorities, upcoming events, seasonal patterns
- Draft weekly content calendar: what, where, when
- Present calendar to Chairman for approval
Tuesday-Thursday: Production (Green + Red-Orange)
- Write content per approved calendar
- 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)
- Present batch to Chairman for review
Friday: Scheduling (Blue)
- Finalize approved content
- Format for each platform
- 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)
