How this command is triggered — by the user, by Claude, or both
Slash command
/copywriter:plan [month] [focus topic]sonnetThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /copywriter:plan
Stop posting randomly. Build a cohesive narrative strategy.
## Usage
## Workflow
1. **Triggers** `content-calendar-planner`.
2. **Reads** `data/2-Domaines/business-profile.json` (to align with offers).
3. **Generates** the "Waterfall Strategy":
- 1x Hero Asset (Blog/Newsletter).
- 3x Social Splinters (LinkedIn/Twitter).
- 1x Personal Story.
4. **Outputs** a Markdown Table Grid + Task List.
---
## 🔗 Solo Integration (Ecosystem Mode)
After generating the content calendar, save to the shared path so Solo agents can read it:
**Result**: Solo's `mo...Stop posting randomly. Build a cohesive narrative strategy.
/copywriter:plan "March" "Launch of Course"
/copywriter:plan "Next Week" "Authority Building"
content-calendar-planner.data/2-Domaines/business-profile.json (to align with offers).After generating the content calendar, save to the shared path so Solo agents can read it:
SOLO_ROOT = "${CLAUDE_PLUGIN_ROOT}/../solo"
solo_installed = file_exists(f"{SOLO_ROOT}/.claude-plugin/plugin.json")
# Also read 0-Inbox for content triggers from Sales (deal wins, client milestones)
if solo_installed:
CALENDAR_PATH = f"{SOLO_ROOT}/data/2-Domaines/content-calendar.md"
INBOX_PATH = f"{SOLO_ROOT}/data/0-Inbox/"
# Check inbox for content triggers before generating calendar
inbox_triggers = glob(f"{INBOX_PATH}content-trigger-*.md")
if inbox_triggers:
note(f"Found {len(inbox_triggers)} content triggers from Sales — incorporating into calendar.")
for trigger in inbox_triggers:
content = read_file(trigger)
incorporate_trigger_into_calendar(content)
archive_file(trigger) # Move to Archives once processed
else:
CALENDAR_PATH = "data/2-Domaines/content-calendar.md"
save_calendar(CALENDAR_PATH)
log(f"Content calendar saved to: {CALENDAR_PATH}")
Result: Solo's monday-morning-agent reads the calendar every Monday morning and includes scheduled posts in the weekly brief.
npx claudepluginhub jamon8888/cc-suite --plugin Copywriter/planCreates a step-by-step implementation plan from requirements or a PRD markdown file, then waits for user confirmation before any code changes.
/planBreaks project into small verifiable tasks with acceptance criteria, dependencies, checkpoints. Reads spec/codebase, presents plan for review, saves to tasks/plan.md and tasks/todo.md.
/planStarts Manus-style file-based planning: creates task_plan.md, findings.md, progress.md if missing, invokes planning skill, and guides through workflow.
/planInteractively builds Goal, Scope, Metric, and Verify command for an autoresearch run from provided goal description.
/planRestates requirements, assesses risks, creates step-by-step implementation plan with phases, dependencies, complexity estimates, and waits for user confirmation.
/planCaptures user intent, analyzes requirements, and generates a weighted execution plan saved to .claude/session-plan.md. Does not execute — plans are saved for review or later execution via /octo:embrace.