본문으로 건너뛰기
cccskills
무료GitHub에 공개

strategy-builder

[Content] Use when a workflow step or the user asks for marketing strategy: positioning, channels, messaging, campaigns, budget and KPIs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Quick Summary

Goal: Build comprehensive marketing strategy with positioning, channels, messaging, campaigns, budget, and KPIs.

Summary:

  • Main path: load the market-analysis artifact → define positioning and differentiation → plan channels with budget and ROI → craft messaging → build the campaign roadmap with KPIs → assess risks and mitigations.
  • Evidence gate: base positioning on competitive analysis, label market evidence, cite every factual claim inline [N] mapped to a Sources row, and make KPIs specific, measurable, and time-bound.

Workflow:

  1. Load market analysis — Read market-analysis output
  2. Define positioning — Value proposition, differentiation
  3. Plan channels — Strategy with budget allocation + ROI
  4. Craft messaging — Tagline, key messages, proof points
  5. Build campaign roadmap — Phases with timeline and KPIs
  6. Risk assessment — Marketing risks with mitigation

Key Rules:

  • Positioning MUST ATTENTION reference competitive analysis
  • Every channel: purpose, budget %, expected ROI, priority
  • KPIs must be specific, measurable, time-bound
  • Market evidence must be labelled as the exact market-analysis artifact or as unverified inline context; never silently treat the latter as reviewed research
  • Every factual claim and number ends with an inline [N] citation mapped to a Sources row (Title, URL, Author/Org, Date, Tier); reuse the market-analysis Sources rows for market facts. Factual claims rest on 2+ independent sources; a single-source claim is marked unverified and held below 60% confidence. Planning choices you set (budget split, KPI targets) state their basis as labelled assumptions

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

Contents

Strategy Builder

Step 1: Load Market Analysis

When invoked by workflow-research marketing mode, read the exact parent-provided MARKET_ANALYSIS_PATH; never derive a second slug. If that workflow artifact is missing, mark market facts N/A and cap market-evidence confidence at 60% — do not silently substitute inline context. Standalone inline context is allowed only when labelled Unverified inline market context. In that mode, do not claim it is the market-analysis artifact, do not introduce uncited market-size figures, mark unsupported market facts N/A, and cap market-evidence confidence at 60%. Extract only what the evidence provenance supports: competitor landscape, target segments, SWOT, and market size.

Step 2: Positioning

Based on competitive analysis:

  • Value proposition — What unique value do we offer?
  • Differentiation — How are we different from competitor X, Y, Z?
  • Brand voice — Tone, personality, communication style

Step 3: Channel Strategy

For each channel:

ChannelPurposeBudget %Expected ROIPriority
{channel}{awareness/acquisition/retention}{%}{X:1}P0/P1/P2

Total budget % must equal 100%.

Step 4: Messaging Framework

  • Tagline — One memorable line
  • Key messages (3-5 pillars) — Core themes
  • Proof points — Evidence supporting each message
  • Elevator pitch — 30-second version

Step 5: Campaign Roadmap

PhaseTimelineObjectiveTacticsKPIsBudget
LaunchM1-M3Awareness{list}{metrics}{$}
GrowthM4-M6Acquisition{list}{metrics}{$}
ScaleM7-M12Retention{list}{metrics}{$}

Step 6: Risk Assessment

RiskLikelihoodImpactMitigation
{risk}H/M/LH/M/L{strategy}

Output

Write to docs/knowledge/strategy/marketing/{descriptive-slug}.md using enforced template from .claude/templates/marketing-strategy-template.md. List every cited source in its Sources table with Title, URL, Author/Org, Date and Tier; every [N] resolves to a row and every row is cited.


[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting.

Closing Reminders

IMPORTANT MUST ATTENTION Goal: Build comprehensive marketing strategy with positioning, channels, messaging, campaigns, budget, and KPIs.

IMPORTANT MUST ATTENTION Main steps: load market analysis → define positioning → plan channels, budget, and ROI → craft messaging → build campaign roadmap and KPIs → assess risks and mitigations.

IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting

IMPORTANT MUST ATTENTION cite every factual claim and number inline [N] mapped to a Sources row (Title, URL, Author/Org, Date, Tier); reuse the market-analysis Sources rows for market facts IMPORTANT MUST ATTENTION back factual claims with 2+ independent sources; mark a single-source claim unverified and hold it below 60% confidence IMPORTANT MUST ATTENTION add a final review todo task to verify work quality

[TASK-PLANNING] Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using TaskCreate.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

[Documentation] Use when generating, smart-merging or refactoring the root AI context (CLAUDE.md, AGENTS.md) and its Claude/Codex projections. Config file only: project-config.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

duc01226/EasyPlatform122026년 10월 20일 업데이트

[Code Quality] Use when a workflow step or the user asks for AI code or plan review: LLM calls, prompts, agents, RAG, evals and guardrails. --mode={code|plan}; --report-only is read-only.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

duc01226/EasyPlatform122026년 10월 20일 업데이트

[Architecture] Use when a workflow step or the user asks for architecture design, compliance review, scalability grading or whole-project audit via --mode={design|review|scalability|full}.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

duc01226/EasyPlatform122026년 10월 20일 업데이트

[Content] Use when a workflow step or the user asks for product/feature ideation with ranked opportunities and validation tests. --mode={roadmap|scope}.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

duc01226/EasyPlatform122026년 10월 20일 업데이트

[Content] Use when a workflow step or the user asks for business viability: Business Model Canvas, financials, risks and go-to-market recommendation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

duc01226/EasyPlatform122026년 10월 20일 업데이트

[Code Quality] Use when a workflow step or the user asks for a focused code-change review: staged, unstaged, branch diff or simple pull request. --fix-loop fixes and re-reviews. Complex pull request: workflow-review-changes; rationale: why-review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

duc01226/EasyPlatform122026년 10월 20일 업데이트

duc01226의 스킬 모두 보기

이 스킬의 문제 신고