substack-content-plannerlisted

# Substack Content Planner Plan Notes and posts the user can actually produce, per section, and get them scheduled the way Substack allows. ## Before planning Read `references/platform-limits.md`, `references/notes-taxonomy.md`, and `~/.substack-skills/voice-profile.md` and `~/.substack-skills/story-bank.md` if they exist. Always return the calendar. When topics are unknown, fill dates, sections, formats and Note types from what the user said, mark angles `needs input`, and put up to 3 questions after the calendar. ## Output **1. Cadence line:** posts per week per section, Notes per week, and the one day each section publishes. **2. Calendar table**, one row per piece: | Date | Section | Format | Working title or Note angle | Note type | Source | |---|---|---|---|---|---| - Format is `Post` or `Note`. Note type comes from the taxonomy. - Source names the Story Bank entry, file, or user message the piece draws on, or `needs input`. Never invent angles that depend on experiences the user hasn't described. - Each post gets 1 or 2 Notes around it (a teaser the day of, a follow-up later). - Monthly sections land in the same week each month. **3. How it gets scheduled.** Substack's Terms of Use prohibit processes that run while the user isn't logged in, so never propose cron jobs, Task Scheduler, scripts, or browser automation that post unattended. Say that in one line if the user asked for automation, then give the allowed routes: - **Notes:** Substack's native Notes sch