메뉴
Builds a go-to-market plan for a product — positioning, ICP, channel mix, messaging, and campaign calendar. Use when launching a product, planning marketing, choosing channels, or aligning the growth team on what to say and where.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | growth-strategy |
| description | Builds a go-to-market plan for a product — positioning, ICP, channel mix, messaging, and campaign calendar. Use when launching a product, planning marketing, choosing channels, or aligning the growth team on what to say and where. |
Marketing without strategy is random posting. Before content, ads, or outreach, define who you're for, what problem you solve, where they hang out, and what success looks like. This skill is the planning layer for the Grow phase — it hands a campaign brief to [[content-marketing]], [[social-distribution]], [[seo-growth]], and [[community-engagement]].
Pairs with [[product-brief]] for product truth, [[launch-readiness]] when GTM aligns with a ship date, [[idea-shaping]] when positioning is still fuzzy, and [[observability]] for funnel metrics.
Skip when you already have an approved campaign brief and only need execution (load the channel skill directly).
Work in order. Don't write posts until positioning and ICP are written down.
Document:
If any of these are unknown, ask — do not invent positioning.
For developer products, be specific:
| Field | Example (developer-connection) |
|---|---|
| Who | Mid-level devs, bootcamp grads, career switchers |
| Job to be done | Find mentors, collaborators, or job referrals |
| Where they are | LinkedIn, X, Reddit (r/cscareerquestions), Discord, Dev.to |
| What they search | "developer networking", "find coding mentor", "dev community" |
| Objections | "Another LinkedIn?", "No one will respond", "Spammy" |
| Trigger moment | New job search, learning a stack, moving to a new city |
Write 1–2 ICP personas max for the first campaign — not five vague segments.
Fill the positioning canvas:
Draft 3 message pillars (themes every piece of content reinforces):
Define voice: technical but friendly, no hype, show-don't-tell, developer-respectful.
Score channels for this ICP and goal (High / Medium / Low / Skip):
| Channel | Best for | Effort | Priority |
|---|---|---|---|
| SEO / blog | Long-term traffic, intent | High | |
| X / Twitter | Dev audience, threads, launches | Medium | |
| Professional networking, B2B dev | Medium | ||
| Authentic discussion, feedback | Medium | ||
| Dev.to / Hashnode | Technical tutorials | Medium | |
| YouTube / Loom | Demos, walkthroughs | High | |
| Discord / Slack communities | Engagement, support | Ongoing | |
| Hacker News / Product Hunt | Launch spikes | One-shot | |
| Email / newsletter | Retention, nurture | Medium | |
| Paid ads | Scale (when organic works) | $$$ |
Pick 2 primary channels and 1–2 secondary for the first 30 days. Spreading across six channels with no depth fails.
Build a week-by-week plan:
| Week | Theme | Content (→ content-marketer) | Social (→ social-media-manager) | SEO (→ seo-strategist) | Community (→ community-manager) |
|---|---|---|---|---|---|
| 1 | Launch / awareness | Launch blog post | Daily posts + launch thread | Landing page + meta | Intro post in 2 communities |
| 2 | Problem education | "Why dev networking fails" | Pain-point threads | Target keyword article | AMA or office hours |
| 3 | Social proof | User story / case study | Testimonial clips | FAQ page | Highlight member wins |
| 4 | Activation | "First connection in 5 min" guide | Demo GIF / video | Long-tail how-to posts | Engagement challenge |
Each row must have owner agent, deliverable, and success metric.
Define north-star and supporting metrics:
| Metric | Tool | Target (30 days) |
|---|---|---|
| Unique visitors | Analytics | |
| Sign-ups / installs | Product analytics | |
| Activation (first key action) | Product analytics | |
| Engagement (DAU/WAU, posts, replies) | Platform + social | |
| Content performance | Views, time on page, shares | |
| SEO | Impressions, clicks (Search Console) |
Schedule weekly review: what worked, what to cut, what to double down on.
Produce one brief per channel agent:
Strategy is done when:
Meta-skill that routes a task to the right engineering skill. Load this at the start of a session or when unsure which skill applies — it maps intent to the process that should govern the work.
Catches breaking changes between services before they ship, by testing the contract each consumer actually depends on instead of spinning up the whole system. Use when services deploy independently, when a provider API change could break a consumer, or when end-to-end integration tests are too slow and flaky to guard every service boundary.
Proves whether a change actually moves the metric, with a valid A/B test instead of a guess — a hypothesis, a primary metric, a pre-computed sample size, guardrail metrics, and an honest readout. Use when shipping a change meant to improve a number (conversion, retention, performance), running an A/B or holdout, or deciding whether a feature "worked."
Decouples deploy from release using feature flags — ship code dark, roll out gradually, kill instantly, and remove the flag once it's done. Use when releasing risky or large changes, rolling out by percentage/cohort, delivering A/B variants, or when stale flags are accumulating as debt.
Finds security risks at design time — before code exists — by mapping the system, enumerating how it could be attacked, and deciding what to do about each threat. Use when designing a feature that touches auth, data, money, or external input, when changing a trust boundary, or when a security-sensitive change needs a structured risk pass rather than a code-level review.
Designs durable, curated memory that an agent carries across sessions — what to persist, how to scope and retrieve it, and how to stop it from drifting or poisoning later runs. Use when an agent needs to remember decisions, preferences, or project facts beyond one context window, or when stale/over-generalized memory is corrupting its behavior.
