'strategy' 검색 결과

Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for AI-citation SEO), content scoring targets, measurement framework, and content differentiation through original research and first-hand experience. Use when user says "blog strategy", "content strategy", "blog positioning", "what should I blog about", "blog topics", "content pillars", "blog ideation".

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

Create comprehensive business strategy with premise deconstruction, business model stress test, pricing, go-to-market plan, and competitive positioning. Runs a 4-layer premise audit before strategy, then generates a full market research report with SWOT, 4P, 10-point business model validation, and constraint analysis. Use when the user has an idea and needs a strategic plan, competitive analysis, pricing strategy, GTM plan, or says 'business plan', 'strategy', 'pricing', 'go-to-market', or 'competitive analysis'.

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

When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.

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

When the user wants open source strategy, OSS commercialization, or open source growth. Also use when the user mentions "open source strategy," "OSS strategy," "open source commercialization," "open source to paid," "open core," "COSS," "commercial open source," "GitHub stars strategy," "DevHunt," "open source marketing," "open source growth," "Llama," "Dify," "Cursor," "open source business model," or "developer tools directory." For GitHub tactics, use github.

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

A discipline for running paid media that does not light money on fire. Hypothesis writing for paid spend, channel selection, budget allocation, audience targeting, bid strategy, campaign types, what NOT to spend on, attribution reality, and the failure modes that produce expensive lessons. Triggers on paid media strategy, ad budget allocation, channel selection, paid media plan, audit my Google Ads, audit my Meta Ads, scale paid media, kill underperforming campaign, paid media hypothesis, ad spend strategy, attribution reality, performance marketing strategy. Also triggers when a team is asking how to scale paid media, or whether to add a new channel, or how to reallocate spend across channels.

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

Builds a product strategy and stress-tests your moat, then writes a one-page strategy doc (diagnosis, where to play, how to win, guiding policy, coherent actions, moat verdicts). Use for 'we need a product strategy', 'is our moat real', 'do we have a competitive advantage', 'where should we play', 'defensibility', 'should we expand into X', 'our roadmap has no strategy', or 'write a product vision'. Draws on 909 insights from 236 Lenny's Podcast guests incl. Roger Martin, Richard Rumelt and Hamilton Helmer.

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

Options trading strategy analysis and simulation tool. Provides theoretical pricing using Black-Scholes model, Greeks calculation, strategy P/L simulation, and risk management guidance. Use when user requests options strategy analysis, covered calls, protective puts, spreads, iron condors, earnings plays, or options risk management. Includes volatility analysis, position sizing, and earnings-based strategy recommendations. Educational focus with practical trade simulation.

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

Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.

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

A great product that nobody knows about is a failed product. Go-to-market strategy is how you get your product into customers' hands. Not marketing in the abstract - specific motions, channels, and sequences for your specific situation. This skill covers GTM motion selection (product-led, sales-led, community), channel strategy, launch sequencing, early customer acquisition, and the critical transitions between GTM phases. Use when "go to market, GTM, launch strategy, how to get customers, sales vs product-led, channel strategy, market entry, customer acquisition, distribution strategy, product launch, getting first customers, sales motion, bottoms up, top down sales, go-to-market, gtm, launch, product-led-growth, sales, channels, customer-acquisition, distribution, marketing" mentioned.

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

Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for GEO), content scoring targets, measurement framework, and content differentiation through original research and first-hand experience. Use when user says "blog strategy", "content strategy", "blog positioning", "what should I blog about", "blog topics", "content pillars", "blog ideation".

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

Win #1 Product of the Day on Product Hunt. Completely reverse-engineered from 30x daily winner and 3x weekly winner campaigns — ranking algorithm decoded, launch timing optimized, hunter selection guide, community engagement approach, and post-launch momentum playbook. Use this if you're: (1) already read PH launch guides but still can't break into Top 5 and need algorithm-level deep optimization, (2) targeting Daily #1 and 5,000+ sign-ups with a proven 30+ case validated approach, or (3) an investor/accelerator coaching portfolio companies on PH launches. What's inside: PH ranking algorithm decoded: weighted factors for first 3 hours, 24 hours, and weekly ranking · Pre-launch preparation: gallery optimization, product URL selection, tagline refinement (≤60 chars) · Launch timing optimization: exact PST launch windows + scheduling guide · Community engagement KPIs: upvote targets, comment response time, maker comment strategy · Platform compliance guide: understanding PH's quality signals and organic growth · Post-launch 72-hour plan: maintaining momentum, conditions for Weekly #1 · Case studies: 3 different categories (AI Tool, App, SaaS) dissected Expected outcomes: Product Hunt Daily #1 ranking · strong community engagement on launch day · 3,000–10,000+ sign-ups (depending on product-market fit) 🇨🇳 Product Hunt 打榜完整攻略 | 🇯🇵 Product Hunt ローンチガイド | 🇰🇷 Product Hunt 런칭 가이드 Keywords: Product Hunt #1, Product Hunt launch strategy, PH ranking algorithm, PH #1 daily winner, Product Hunt tips, product launch, startup launch, ranking optimization, PH gallery optimization, Community engagement strategy, maker community engagement, product strategy, launch tactics, how to win Product Hunt, product hunt best practices

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

Use when the user wants to build or think through a strategy via guided conversation — for a company, product, team, career, or initiative. Triggers on "help me figure out our direction", "what should we focus on", strategic planning, competitive positioning, go-to-market strategy. Also catches indirect requests like prioritization struggles or "we have too many priorities". Does NOT review existing strategy documents (use strategy-review) or brainstorm project features (use brainstorm-beagle).

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

Strategic marketing leadership guidance for B2B SaaS and technology companies. Covers go-to-market strategy, product marketing, content marketing, demand generation, SEO, community building, event marketing, PR, partnerships, and pricing strategy. Use when planning marketing strategy, launching products, building brand awareness, driving demand, or scaling marketing operations. Use for "marketing plan", "GTM strategy", "content strategy", "demand gen", "product launch marketing".

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

Use this skill when designing a product catalog taxonomy, planning attribute strategy, or determining search and navigation structure for a B2B or B2C/D2C Commerce store. Triggers on: taxonomy design questions, attribute planning, search index strategy, category navigation structure, or merchandising hierarchy decisions. NOT for wiring the catalog itself — WebStoreCatalog, entitlement policies, product assignment — use admin/commerce-product-catalog. NOT for configuring searchable or facetable attributes, sort rules and index rebuilds — use apex/commerce-search-customization.

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

Strategy map analysis using the Eterdis two-directional causal chain. Use this skill to diagnose whether strategy is coherent by building two chains — bottom-up from resources to results, top-down from expectations to requirements — and finding where they don't connect. Runs in three modes — full diagnostic for deep sessions, review mode for quick re-assessment, and alert triggers for early-warning signals. Updates company-context.md after every run. Triggers on questions about strategic alignment, why the strategy isn't working, what to invest in, how the business creates value, whether the plan is realistic, or where the biggest gap is. Based on practice by Eterdis (eterdis.com).

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

Classify market conditions as bullish, bearish, ranging, or volatile to guide strategy selection and historical testing. Distinguish synthetic demonstrations from analysis of actual price data, with confidence levels and historical comparisons where available.

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

• Reviewing market conditions for a stock symbol
• Choosing a strategy suited to market conditions
• Checking market conditions before a backtest

Decide what content to create using customer questions, keyword data, and competitor coverage. The skill produces core themes, related topic maps, ranked content ideas, and calendar and distribution guidance aligned with business goals and available resources.

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

• Choose topics and priorities for a business blog
• Turn customer conversations into content ideas
• Group keyword data into related topics

Browse registered trading strategies and compare evidence from backtests, which simulate trades on historical data. Filter by market conditions, trade counts, risk-adjusted returns, and cost feasibility, inspect evidence age, and rebuild the evidence cache from local runs.

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

• Browsing registered trading strategies
• Finding strategies with evidence for falling or rising markets
• Checking a strategy's evidence quality and age

Design or review SaaS pricing by choosing what customers pay for, defining plan features, and assessing price points. Create pricing page outlines, customer research questions, and price increase plans with communication templates and risk scenarios.

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

• Designing pricing plans for a new SaaS product
• Reviewing existing prices and plan features
• Planning a price increase and customer notices

Plan free calculators, generators, and checkers for marketing. Compare ideas by search demand, competition, and effort, then define the user flow, lead capture, landing page, launch activities, and measurement plan to assess results.

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

• Compare free tool ideas before committing development time
• Design useful results and an email capture flow
• Plan a tool landing page and launch activities

Plan what content to create using business goals, customer questions, and competitor gaps. Organize related topics, prioritize ideas for search or sharing, and turn them into content calendars or briefs with clear audiences and purposes.

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

• Planning core themes for a company blog
• Prioritizing topics from customer questions
• Grouping related articles into topic clusters

Plan organizational changes such as tool migrations, restructures, and strategy shifts using ADKAR, a five-stage model for adopting change. Structure communication, training, and follow-up while addressing employee concerns, resistance, and fatigue from overlapping changes.

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

• Plan communication and training for a tool migration
• Prepare reorganization announcements and employee FAQs
• Explain a strategy shift and its impact on teams

Guide product strategy for growing companies by assessing customer fit, product investment priorities, and team structure. Produces scorecards, portfolio recommendations, organization proposals, and board reporting materials to support decisions about what to build and fund.

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

• Defining a product vision for the next three to five years
• Assessing product fit using retention and customer feedback
• Choosing which products to invest in, maintain, or retire

Build a product launch strategy from product and market research. Define marketing channels, audience messages, measurable goals, and launch milestones, then organize them into a practical 90-day roadmap with risks and decision points.

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

• Planning a new product launch
• Preparing to enter a new market
• Choosing marketing channels and messages