Localized reading guide
campaign-planPurpose, usage and source
Generate a full campaign brief with objectives, audience, messaging, channel strategy, content calendar, and success metrics. Use when planning a product launch, lead-gen push, or awareness campaign, when you need a week-by-week content calendar with dependencies, or when translating a marketing goal into a structured, executable plan.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
marketing/skills/campaign-plan/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Agent workflows
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Generate a full campaign brief with objectives, audience, messaging, channel strategy, content calendar, and success metrics. Use when planning a product launch, lead-gen push, or awareness campaign, when you need a week-by-week content calendar with dependencies, or when translating a marketing goal into a structured, executable plan.
How the upstream workflow works
Calendar Planning Process
Start with milestones: campaign launch, event dates, product releases, seasonal moments Work backward: what needs to be live and when? What is the production lead time? Map content to funnel stages: ensure coverage across awareness, consideration, and conversion Batch by theme: group related content pieces into weekly or bi-weekly themes
Upstream passage · L205 ↗1. Campaign Overview
Campaign name suggestion One-sentence campaign summary Primary objective with a specific, measurable goal Secondary objectives (if applicable)
Upstream passage · L40 ↗10. Next Steps
Immediate action items to kick off the campaign Stakeholder approvals needed Key decision points
Upstream passage · L108 ↗Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Campaign Plan
- Trigger
- Inputs
- Campaign Brief Structure
- 1. Campaign Overview
- 2. Target Audience
- 3. Key Messages
- 4. Channel Strategy
- 5. Content Calendar
- 6. Content Pieces Needed
- 7. Success Metrics
- 8. Budget Allocation (if budget provided)
- 9. Risks and Mitigations
- 10. Next Steps
- Campaign Framework: Objective, Audience, Message, Channel, Measure
- Objective
- Audience
- Message
- Channel
- Measure
- Channel Selection Criteria
- Calendar Planning Process
- Content Cadence Guidelines
- Production Timeline Benchmarks
- Percentage of Revenue Method
- Channel Allocation Framework
- Budget Optimization Principles
- Output
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
f0b146074b64ee0fd52f7864e30191eab83878c8c1e3e7cf24754e13c7dbfad3