Build a coordinated marketing, growth, go-to-market, fractional-CMO, 90-day, or annual plan: diagnosis summary, strategic thesis and its sacrifice, initiatives with owners and budgets, team and partner model, measurement, dependencies, stop rules, and operating cadence. Use when the user needs a plan rather than one tactic; run constraint-diagnosis first when the current constraint is unknown.
Installs into .claude/skills of the current project.
Are you the author of Growth Plan?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mtent-growth-plan)
---
name: growth-plan
description: Build a coordinated marketing, growth, go-to-market, fractional-CMO, 90-day, or annual plan: diagnosis summary, strategic thesis and its sacrifice, initiatives with owners and budgets, team and partner model, measurement, dependencies, stop rules, and operating cadence. Use when the user needs a plan rather than one tactic; run constraint-diagnosis first when the current constraint is unknown.
license: MIT
metadata:
version: "2.0.0"
author: MTEnt
---
# Growth Plan
Create a decision system, not an impressive-looking catalog. The plan must show the constraint, the chosen thesis, executable work, and the evidence that changes course.
If `.agents/marketing-context.md` exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read [planning-system.md](references/planning-system.md) for the three phases, the thirteen-section plan, budget method, stage patterns, and team model.
## Operating contract
1. Inspect product truth, audience evidence, offer, baseline, economics, team capacity, previous work, and measurement quality.
2. Take the current constraint from `$constraint-diagnosis`; do not assign channel work before it exists.
3. Compare the status quo with credible strategic alternatives; choose one primary thesis and state what it sacrifices.
4. Build near-term initiatives from actual capacity; keep later work conditional on signal.
5. Give each initiative an outcome, owner, artifact, dependency, cost or effort boundary, metric, threshold, review point, and failure response; model forecasts as labeled scenarios.
6. Walk consequential positioning, budget, staffing, or claim decisions through the user before treating them as settled.
Do not spend, hire, publish, or change live systems without explicit authorization, and do not use arbitrary budget splits or treat platform-reported return as incremental profit.
## Return
The complete plan in the requested format plus unresolved decisions.