비즈니스 스킬

Run all four review skills (investor, customer, operator, skeptic) on a business plan in sequence, then auto-decide where verdicts agree and surface only disagreements + taste decisions to the user. One command = full review gauntlet, intelligently filtered. Use when a plan is ready to be stress-tested before commit. Triggered by: 'panel review', 'review panel', 'run all reviews', 'review gauntlet', '审议会', '四方评审'.

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

Automated outreach and sales pipeline — cold email sequences, partnership outreach, lead generation, and prospect management. Use when the user needs cold email campaigns, sales sequences, lead generation, partnership outreach, B2B sales, or says 'cold email', 'outreach', 'lead gen', 'find prospects', 'sales sequence', or 'partnerships'.

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

Financial tracking, revenue analytics, expense management, and pricing optimization. Integrates with Stripe for revenue data, tracks unit economics, and generates financial reports. Use when the user needs revenue tracking, financial reports, pricing optimization, expense management, or says 'revenue', 'MRR', 'ARR', 'finances', 'pricing', 'expenses', 'profit', 'ROAS', or 'unit economics'.

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

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

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

Restore a prior business-state snapshot saved by /money-save, so you can continue from exactly where the last session left off. Loads the most recent snapshot for the current project (auto-detected from the working directory), or a specific one by index. Use when starting a new Claude Code conversation and the user wants to continue prior work. Triggered by: 'continue from last time', 'where did we leave off', 'pick up from before', 'resume', '接着上次', '续上', '之前的结论', '上次诊断到哪了'.

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

Review a business plan from the perspective of a hostile devil's advocate. Asks: what kills this in month 6? What's everyone politely not mentioning? Outputs a verdict — EXISTENTIAL RISK / SOLVABLE RISKS / LOW-RISK / WRONG QUESTION. Use after the investor/customer/operator reviews are done, as the final gauntlet before committing real time and money. Triggered by: 'skeptic review', 'devil's advocate', 'what would kill this', 'red team this', '泼冷水', '杀手在哪'.

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

Save the current business state to disk so future Claude Code sessions can pick up where you left off. Captures confirmed conclusions, ruled-out directions, open hypotheses, and the next recommended skill. Use when the user has just reached a conclusion in /money-discover, /money-strategy, /money-diagnose, or any pipeline phase, and wants to lock the state in. Also triggered by: 'save this', 'checkpoint', 'remember this', 'lock it in', '保存', '存档', '记下来', '这个结论留着'.

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

Deep business diagnosis for when things aren't working. Uses Socratic questioning, first-principles reasoning, and constraint analysis to find WHY a business is stuck — not just prescribe solutions. Use when the user says 'my business isn't working', 'I'm stuck', 'what's wrong', 'diagnose my business', 'why am I not growing', 'help me figure out the problem', or describes a specific business challenge.

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

American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.

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

British business English writing style for professional communications — polished, understated, EN-GB spelling (colour, organise, centre). Use whenever the user is writing for a British audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.

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

New Zealand business English writing style for professional communications — warm, inclusive, EN-NZ spelling (colour, organise, centre). Use whenever the user is writing for a New Zealand audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.

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

Write structured strategic documents for small and medium businesses: SWOT analyses, lean business plans, OKRs, competitive analyses. Each mode has a defined structure and quality bar. Use whenever a business asks to articulate strategy, set goals, analyse competition, plan for growth, do a SWOT, write OKRs, or build a lean business plan. Produces actionable documents, not generic frameworks.

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

Write compelling award submissions, grant applications, and competition entries. Maps achievements to selection criteria using evidence-based narratives. Use whenever the user is applying for a business award (Telstra, chamber of commerce, industry awards), a grant, a competition, or any submission demonstrating merit against defined criteria.

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

Australian business English for professional writing — warm, direct, EN-AU spelling (colour, organise, centre), no filler words. Use whenever the user is writing for an Australian audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.

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

商务专业风信息图生成。支持风格预设、配色、图标、布局、密度等参数化控制。手动触发。

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

前后端接口契约安全规范，适用于接口新增或调整、联调、列表分页异常与临时兼容治理；用于避免响应结构漂移被前端兼容长期掩盖。

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

When the user wants to plan, design, or optimize pricing strategy and structure. Also use when the user mentions "pricing strategy," "pricing model," "pricing tiers," "freemium," "value-based pricing," "anchoring," "price structure," or "monetization strategy." For pricing page, use pricing-page-generator.

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

When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.

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

When the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.

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

When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start," "cold start problem," "first users," "seed users," "finding users," "finding early users," "Fiverr Upwork," "comment outreach," "Twitter search users," "product launch strategy," "0 to 1 growth," "early-stage acquisition," "launch channels," "get first customers," "Product Hunt launch," "AppSumo," "LTD," "indie hacker," "bootstrapping," or "solo founder." For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy.

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

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.

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

Plan, audit, implement, migrate, or validate localization for multilingual products and websites, including locale scope, market readiness, URL architecture, content coverage, hreflang coordination, rollout, and production verification. Use translation for the actual translation, glossary, and language review work.

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

When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.

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

When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.

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