Produce the 11-section Growth Plan — the flagship Part 8 client-facing deliverable that synthesises the entire engagement into a single executable strategy.
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill growth-plan
The Growth Plan is the flagship client-facing deliverable. It synthesises every internal document produced in Parts 1–7 into a single 11-section narrative answering: *"How will we grow this business digitally, and what will it cost?"*
Heavy skill. Grep before Read any referenced file, then Read only matched ranges with offset + limit. List the brand's data dir (~/.claude-marketing/brands/{slug}/, or $CLAUDE_PLUGIN_DATA/digital-marketing-pro/brands/{slug}/ when that env var is set) before opening files. On re-invocation mid-session, skip files already in context.
Specification: growth-plan-template.md — the canonical 11-section structure.
Before producing the Growth Plan, verify:
If any pre-condition fails, do NOT produce. Instruct the user.
| # | Section | Length | Source |
|---|---------|--------|--------|
| 1 | Executive Summary | 1 page | Synthesis |
| 2 | Business Context | 2-3 pages | Core Doc 3.1 + Part 4.4 + Part 4.2 |
| 3 | Target Audience | 2-3 pages | Core Doc 3.2 |
| 4 | Strategic Positioning | 2 pages | Core Doc 3.3 |
| 5 | Channel Strategy | 3-4 pages | Core Doc 3.4 + Part 9 channel docs |
| 6 | Budget & Media Plan | 2-3 pages | Core Doc 3.4 Step 5 + 9 |
| 7 | KPI Framework | 2 pages | Part 7 KPI tree |
| 8 | Implementation Timeline | 2-3 pages | Part 7 + 30/60/90 framework |
| 9 | Team & Resource Plan | 1-2 pages | Engagement context |
| 10 | Risk & Contingency | 1-2 pages | Core Doc 3.1 Step 16 |
| 11 | Expected Outcomes | 2 pages | Three-scenario forecasting |
Total target length: 20–30 pages. Beyond 30, clients stop reading.
Reading order (canonical version of each):
The Growth Plan is synthesis, not concatenation. Do not copy paragraphs from the Core Docs verbatim. Re-write each section in client-facing narrative form, citing the source document for traceability.
Section 11 (Expected Outcomes) presents Conservative / Moderate / Aggressive scenarios per three-scenario-forecasting.md.
Section 7 (KPI Framework) targets are also presented as three scenarios per KPI.
Section 5 (Channel Strategy) and Section 6 (Budget & Media Plan) explicitly call out the In-Market vs Out-Market budget allocation per in-market-out-market.md.
Section 8 (Implementation Timeline) uses the 30/60/90 phasing per 30-60-90-framework.md for the first quarter, then quarterly milestones thereafter.
Save to engagements/{id}/part-08-growth-plan/growth-plan.md. Generate companion exports:
pdf-generator.py scriptThe CEO reads this. Make it count.
Set the stage for why the strategy is what it is.
30 / 60 / 90-day milestones for the first quarter. Quarterly milestones thereafter.
/digital-marketing-pro:yearly-planner must align with this Growth Planpart-08-growth-plan/growth-plan.md*SYNTHETIC EXAMPLE — fabricated for illustration; never reuse these numbers. The INR forecast figures below are made up.*
User: Produce the Growth Plan for Acme.
Skill response:
1. Verify pre-conditions: Parts 1-7 completed, Core Docs at v2 ✓
2. Pull from source docs ONE AT A TIME via targeted Read with offset+limit (grep first for the section you need, then Read just that range) — the full corpus is ~95K words, so bulk-reading every doc up front blows the per-skill 5K-token budget
3. Synthesise into 11 sections, ~24 pages
4. Apply three-scenario forecasting in Sections 7 + 11
5. Apply 30/60/90 phasing in Section 8
6. Save markdown + generate PDF + DOCX
7. Mark Growth Plan complete (Yearly Planner pending)
8. Brief: "Growth Plan v1.0 produced. 24 pages. Conservative Q1 forecast: INR 1.8 Cr new ARR; Moderate: INR 2.6 Cr; Aggressive: INR 3.4 Cr. Run /digital-marketing-pro:yearly-planner next."
engagement-workflow — orchestrates Part 8yearly-planner — companion deliverable that completes Part 8four-core-documents — produces the canonical Core Docs that feed the Growth PlanA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.
Materials science toolkit. Crystal structures (CIF, POSCAR), phase diagrams, band structure, DOS, Materials Project integration, format conversion, for computational materials science.
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
Take indranilbanerjee/growth-plan from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.