/growth-plan

name: growth-plan
description: "Produce the 11-section Growth Plan — the flagship Part 8 client-facing deliverable that synthesises Parts 1-7 of the engagement into a single 20-30 page executable strategy with three-scenario forecasts, an In-Market/Out-Market budget split, and a 30/60/90 timeline, exported to PDF and DOCX. Triggers on \"/digital-marketing-pro:growth-plan\", \"produce the growth plan\", \"write the strategy document for the client\", \"run part 8\", \"synthesise the engagement into one deliverable\". Requires Parts 1-7 complete; reads the Four Core Documents, the Living Project Instruction File, and Part 7 prep docs, and pairs with /digital-marketing-pro:yearly-planner."
user-invocable: true
triggers:
  - produce the growth plan
  - generate flagship client deliverable
  - run part 8 growth plan
  - synthesise the engagement into a growth plan
  - write the strategy document for the client
  - 11-section growth plan
allowed-tools: Read Write Edit Bash Glob Grep
engagement-part: "8"
view-preference: v2-primary

/digital-marketing-pro:growth-plan — Part 8 Flagship Deliverable

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?"*

Context efficiency

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](../context-engine/growth-plan-template.md) — the canonical 11-section structure.

Pre-conditions

Before producing the Growth Plan, verify:

1. **Parts 1–7 completed** in the engagement 2. **Four Core Documents at canonical version** (v2 if re-runs happened, v1 otherwise) 3. **Living Project Instruction File current** — reflects the current strategic facts 4. **Part 7 Preparation Documents completed** — campaign architecture, naming conventions, KPI tree, content pillars, asset inventory, approval chains

If any pre-condition fails, do NOT produce. Instruct the user.

The 11 Sections

| # | 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.

Production process

Step 1: Read source documents

Reading order (canonical version of each):

1. Living Project Instruction File (current truth) 2. Core Doc 3.1 Business & SBU Analysis 3. Core Doc 3.2 Segmentation Framework 4. Core Doc 3.3 Brand Positioning & Communications 5. Core Doc 3.4 DMFlow 6. Part 4 documents (4.1, 4.2, 4.3, 4.4) 7. Part 7 preparation documents (campaign architecture, KPI tree, content pillars)

Step 2: Synthesise — do not re-state

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.

Step 3: Apply the three-scenario discipline

Section 11 (Expected Outcomes) presents Conservative / Moderate / Aggressive scenarios per [three-scenario-forecasting.md](../context-engine/three-scenario-forecasting.md).

Section 7 (KPI Framework) targets are also presented as three scenarios per KPI.

Step 4: Apply the In-Market vs Out-Market split

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](../context-engine/in-market-out-market.md).

Step 5: Apply the 30/60/90 framework

Section 8 (Implementation Timeline) uses the 30/60/90 phasing per [30-60-90-framework.md](../context-engine/30-60-90-framework.md) for the first quarter, then quarterly milestones thereafter.

Step 6: Output

Save to `engagements/{id}/part-08-growth-plan/growth-plan.md`. Generate companion exports:

• PDF via the existing `pdf-generator.py` script
• DOCX via the existing document export utilities

Section-by-section guidance

Section 1: Executive Summary

The CEO reads this. Make it count.

• Key findings (3-5 bullets — most important things from analysis)
• Recommended strategy (1-2 sentences headline)
• Expected outcomes (moderate scenario, with conservative-aggressive band)
• Investment required (total budget; fixed + variable breakdown)
• Timeline (30/60/90 + quarterly milestones in one sentence)
• The single most important thing the client needs to know

Section 2: Business Context

Set the stage for why the strategy is what it is.

• Summary of business analysis (Core Doc 3.1) — what the business is, how it makes money, key strengths and constraints
• Industry landscape — market size, growth trajectory, competitive intensity
• Competitive position — where the brand sits, key competitors, positioning today
• Critical assumptions — major Stone facts and validated Opinions

Section 3: Target Audience

• Primary persona summary in actionable format (6 questions)
• Secondary persona if relevant
• Why these personas were chosen (tie back to TG scoring from 3.2)
• Anti-personas —