ideate-month

# /socialforge:ideate-month — the month before the calendar exists SocialForge's pipeline starts at `parse-calendar` — someone hands it a calendar. This skill is for when nobody has: the client asks "what should this month be about?", and that question is the actual work they are paying for. The output is a **draft calendar in the exact shape `parse-calendar` ingests**, so an approved plan flows into production with zero re-typing. ## Inputs — use whichever exist, say which were missing 1. **The brand profile** (required) — pillars, voice, platforms, compliance rules from `brand-config.json`. No profile → stop and run `/socialforge:brand-setup` first. Ideating without pillars produces generic content for nobody. 2. **A theme or business context** (optional) — a launch, a season, a campaign the client named. 3. **Raw signals** (optional) — pasted news, industry threads, competitor moves, sales-call notes, community questions. Mine them; never use them as filler. Every signal either maps to a pillar and a concrete angle, or it is dropped and listed as dropped, with the reason. 4. **Last month's results** (optional) — measured first, anecdote second: - **Measured**: run `python ${CLAUDE_PLUGIN_ROOT}/scripts/ingest_performance.py --action wins --brand {brand} --month {last-month}`. If a `performance.json` exists (built by `/socialforge:ingest-performance` from the platform's own analytics export), this returns winners ranked with a ...