ads-plan▌
agricidaniel/claude-ads · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Example: META_CONV_Prospecting_US_2026Q1
Strategic Paid Advertising Plan
Process
1. Discovery
- Business type, products/services, target audience
- Current advertising status (active platforms, spend, performance)
- Goals: brand awareness, lead generation, e-commerce sales, app installs
- Budget range (monthly/quarterly)
- Timeline and urgency
- In-house team capacity vs agency needs
2. Competitive Analysis
- Identify top 3-5 competitors
- Analyze their ad presence across platforms (Google Ads Transparency, Meta Ad Library)
- Estimate competitor spend levels and platform mix
- Identify messaging themes and creative approaches
- Note keyword/audience gaps (opportunities competitors are missing)
3. Platform Selection
- Load industry template from
assets/directory - Match business type to recommended platform mix
- Read
ads/references/budget-allocation.mdfor platform selection matrix - Read
ads/references/conversion-tracking.mdfor tracking setup requirements - Assess platform fit based on:
- Target audience demographics per platform
- Product/service type suitability
- Budget requirements per platform (minimums)
- Sales cycle length and attribution needs
- Creative capabilities and content availability
4. Campaign Architecture
Naming Convention
[Platform]_[Objective]_[Audience]_[Geo]_[Date]
Example: META_CONV_Prospecting_US_2026Q1
Campaign Structure Template
Account
├── Brand Campaign (always-on, protect brand terms)
├── Non-Brand Prospecting
│ ├── Campaign 1: [Top Funnel - Awareness]
│ │ ├── Ad Group/Set 1: [Audience A]
│ │ └── Ad Group/Set 2: [Audience B]
│ ├── Campaign 2: [Mid Funnel - Consideration]
│ │ ├── Ad Group/Set 1: [Interest-based]
│ │ └── Ad Group/Set 2: [Lookalike/Similar]
│ └── Campaign 3: [Bottom Funnel - Conversion]
│ ├── Ad Group/Set 1: [High-intent]
│ └── Ad Group/Set 2: [Custom audience]
├── Retargeting
│ ├── Website Visitors (7-30 days)
│ ├── Engaged Users (video views, social engagement)
│ └── Cart Abandoners / Form Starters
└── Testing
└── New audiences, formats, or messaging
5. Budget Planning
Monthly Budget Distribution
Read ads/references/budget-allocation.md for the 70/20/10 framework.
| Tier | Allocation | Purpose |
|---|---|---|
| Proven (70%) | Primary platforms with proven ROI | Revenue engine |
| Scaling (20%) | Platforms showing promise | Growth engine |
| Testing (10%) | New platforms or strategies | Innovation |
Budget Pacing
- Month 1-2: heavy testing, expect higher CPA (learning)
- Month 3-4: optimize based on data, tighten targeting
- Month 5-6: scale winners, kill losers, expand
- Ongoing: 70/20/10 maintenance with quarterly reviews
6. Creative Strategy
Content Pillars
- Pain Point: address specific problems your audience faces
- Social Proof: testimonials, case studies, reviews
- Product Demo: show the product/service in action
- Offer: promotions, free trials, lead magnets
- Education: teach something valuable related to your product
Creative Production Plan
| Priority | Asset Type | Platforms | Quantity |
|---|---|---|---|
| P1 | Product/service videos (15-30s) | Meta, TikTok, YouTube | 5-10 |
| P2 | Static images with copy | Google, Meta, LinkedIn | 10-15 |
| P3 | Carousel/collection | Meta, LinkedIn | 3-5 |
| P4 | UGC/testimonial video | TikTok, Meta | 3-5 |
| P5 | Long-form video (1-3 min) | YouTube | 2-3 |
7. Tracking Setup Plan
Before launching any ads, ensure tracking is configured:
| Platform | Client-Side | Server-Side | Priority |
|---|---|---|---|
| gtag.js | Enhanced Conversions, GTM SS | P1 | |
| Meta | Pixel | CAPI | P1 |
| Insight Tag | CAPI (2025) | P2 | |
| TikTok | Pixel | Events API + ttclid | P2 |
| Microsoft | UET Tag | Enhanced Conversions | P2 |
8. Implementation Roadmap
Phase 1: Foundation (Weeks 1-2)
- Install all tracking pixels and server-side tracking
- Set up conversion events and goals
- Create campaign structure and naming conventions
- Build initial audiences (custom, lookalike/predictive)
- Produce first batch of creative assets
Phase 2: Launch (Weeks 3-4)
- Launch campaigns on primary platform(s) first
- Set conservative budgets and bidding (Maximize Clicks / Lowest Cost)
- Monitor daily for the first 7 days
- Verify conversion tracking is firing correctly
Phase 3: Optimize (Weeks 5-8)
- Analyze initial data (minimum 2 weeks of data)
- Adjust bidding strategies based on conversion volume
- Kill underperforming ad groups/creatives (3x Kill Rule)
- Launch secondary platforms
- Begin A/B testing (creative, landing pages, audiences)
Phase 4: Scale (Weeks 9-12)
- Scale winning campaigns (20% rule)
- Expand to testing platforms (10% budget)
- Implement advanced strategies (ABM, Shopping feeds, Smart+)
- Monthly performance reviews
Industry Templates
Load from assets/ directory based on detected or specified business type:
saas.md: SaaS companiesecommerce.md: E-commerce storeslocal-service.md: Local service businessesb2b-enterprise.md: B2B enterpriseinfo-products.md: Info products and coursesmobile-app.md: Mobile app companiesreal-estate.md: Real estatehealthcare.md: Healthcarefinance.md: Financial servicesagency.md: Marketing agenciesgeneric.md: General business template
Output
Deliverables
ADS-STRATEGY.md: Complete strategic advertising planCAMPAIGN-ARCHITECTURE.md: Campaign structure with naming conventionsBUDGET-PLAN.md: Budget allocation with monthly pacingCREATIVE-BRIEF.md: Creative production plan with specificationsTRACKING-SETUP.md: Tracking implementation checklistIMPLEMENTATION-ROADMAP.md: Phased rollout timeline
KPI Targets
| Metric | Month 1 | Month 3 | Month 6 | Month 12 |
|---|---|---|---|---|
| ROAS | Baseline | Target -20% | Target | Target +20% |
| CPA | Baseline | Target +30% | Target | Target -10% |
| CVR | Baseline | +10% | +20% | +30% |
| CTR | Baseline | +15% | +25% | +30% |
| Budget | Testing | Optimizing | Scaling | Maintaining |
How to use ads-plan on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add ads-plan
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches ads-plan from GitHub repository agricidaniel/claude-ads and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate ads-plan. Access the skill through slash commands (e.g., /ads-plan) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★61 reviews- ★★★★★Ira Choi· Dec 8, 2024
I recommend ads-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Lucas Ndlovu· Dec 4, 2024
ads-plan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ishan Chawla· Nov 27, 2024
Useful defaults in ads-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Mia Gupta· Nov 23, 2024
We added ads-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ira Ramirez· Oct 18, 2024
Registry listing for ads-plan matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Min Taylor· Oct 14, 2024
ads-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yash Thakker· Sep 21, 2024
ads-plan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Min Brown· Sep 21, 2024
We added ads-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Noah Kim· Sep 21, 2024
Registry listing for ads-plan matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Mia Thomas· Sep 17, 2024
ads-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 61