비즈니스 스킬

Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.

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

Revenue leadership for B2B SaaS companies. Revenue forecasting, sales model design, pricing strategy, net revenue retention, and sales team scaling. Use when designing the revenue engine, setting quotas, modeling NRR, evaluating pricing, building board forecasts, or when user mentions CRO, chief revenue officer, revenue strategy, sales model, ARR growth, NRR, expansion revenue, churn, pricing strategy, or sales capacity.

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

Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when company context is missing or more than 90 days old — e.g. after a fundraise or pivot.

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

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

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

Build, measure, and evolve company culture as operational behavior — not wall posters. Covers mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, and cultural rituals by stage. Use when building company values, assessing culture health, designing cultural rituals, creating culture codes, handling culture clashes, or when user mentions culture, values, culture debt, founder culture, or culture code.

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

Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when a plan needs hard scrutiny, a board meeting is coming, a painful decision has been avoided, or a failure needs an honest post-mortem.

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

Ranks any list of impediments and their countermeasures using a value-stream scoring model (ROI, Cost to Implement, Ease of Deployment, Risk Factor) and a fixed prioritization formula. Use when someone asks to prioritize, rank, sequence, or triage impediments, countermeasures, remediation items, risks, findings, gaps, action items, or backlog entries; or mentions value-stream prioritization, A3 / lean countermeasure ranking, ROI vs. effort scoring, or building a remediation / improvement backlog. Works with GHQR findings, audit results, retrospective action items, risk registers, architecture review gaps, or any free-form `{impediment, countermeasure}` list.

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

Coaches founders and CEOs on their own development: leadership archetype, delegation, blind spots, and the decisions that change as the company scales. Use when a founder is the bottleneck, struggles to delegate, or is outgrowing their current way of leading.

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

Use when raw SaaS numbers need turning into a health verdict — MRR, ARR, churn, CAC, LTV, payback, burn multiple, NRR. Calculates the metrics, benchmarks them against industry standards, and returns prioritized, plain-English advice as a senior SaaS CFO would.

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

Triggers on keywords M&A, due diligence, post-merger integration, synergy

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

Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, or strategy communication.

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

Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners. Detects narrative contradictions and ensures the same truth is framed for each audience's needs. Use when preparing investor updates, all-hands presentations, board communications, recruiting narratives, crisis communications, or when user mentions company narrative, messaging consistency, storytelling, all-hands, investor update, or crisis communication.

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

Cross-functional what-if modeling for cascading multi-variable scenarios. Unlike single-assumption stress testing, this models compound adversity across all business functions simultaneously. Use when planning for compound downside scenarios (for example losing a key customer while a funding round slips) rather than testing one assumption.

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

Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommendations. Use when assessing overall company health, preparing for board reviews, identifying at-risk functions, or when user mentions org health, health check, or health dashboard.

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

International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.

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

Deploy AI and NLP-powered detection systems to identify business email compromise attacks by analyzing writing style, behavioral patterns, and contextual anomalies that evade traditional rule-based filters.

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

Business Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data,

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

Configures pfSense firewall rules, NAT policies, VPN tunnels, and traffic shaping to enforce network segmentation, control traffic flow, and protect internal network zones in enterprise and small-to-medium business environments.

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

Author a placeable layout block that looks right at ANY pane size. The one hard rule — size to the PANE with container queries (@container), never the viewport — plus list/form playbooks and the sizing contract (minWidth etc.) the viability metric reads. Use when adding/converting a croutonLayoutBlocks block, or when a block overflows/breaks in a narrow pane.

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

Verified lookup pack for crouton's schema→CRUD generation domain — the fieldsFile JSON format, the complete field-type catalog with aliases, the naming contract, the exact artifact list one generate run produces, the seed/default-layout pipeline, dialect defaults, and rollback semantics. Use when writing or reviewing a collection schema, when asking "what field types exist / what does `crouton config` actually generate / where did this file name come from / why did I get a pg schema", when a generated file's name or path doesn't match the docs, or when removing/regenerating a collection. Trigger phrases — "what field types are supported", "schema JSON format", "what files does crouton generate", "naming convention for collections", "rollback a collection", "dialect default". The generation WORKFLOW (steps + sign-off gates) lives in the `crouton` skill — this is the reference it doesn't carry.

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

Capture a POC's signed-off behaviour into its spec ledger (`<poc>/spec.json`) — the structured, walkable behaviour contract graduation freezes as authoritative. Run at the moment a behaviour gets signed off ("ok, this works"), while it's fresh — the same trigger as the HANDOFF.md update, but capturing the *behaviour as a testable entry* rather than the *decision as prose*. Use when a POC behaviour is approved, or asked to "capture this spec", "write the spec entry", "log this to the ledger".

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

The crouton mental model for someone who has never seen this repo — what "layer" means (two different things), the two-halves rule, the three app.config registries, team-scoped multi-tenancy, manifest-driven field types, the numbered invariants with the incidents behind them, and the known-weak points. Use when orienting in this codebase for the first time, when a question is shaped like "how does crouton work / why is it built this way / where does X live", when deciding whether a change belongs in a package or a generated layer, when confused by an extends chain or by croutonApps/croutonCollections/croutonLayoutBlocks, or before proposing any structural change. Trigger phrases: "what is a crouton layer", "package vs generated layer", "how does multi-tenancy work here", "why is there a stub component", "where do field types come from", "what invariants must hold".

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

戦略企画の専門スキル。中期経営計画、新規事業企画、事業ポートフォリオ分析を支援。 SWOT/PEST/Porter 5F分析、ビジネスモデルキャンバス、BCG/GE/Ansoffマトリクスなど MBA標準の戦略フレームワークを活用した体系的な戦略立案を行う。 Use when creating strategic plans, business proposals, portfolio analysis, or when applying strategic frameworks like SWOT, PEST, Porter's Five Forces, BCG Matrix. Triggers include「中期経営計画」「戦略企画」「事業ポートフォリオ」「SWOT分析」 「新規事業企画」「ビジネスモデル」「競争戦略」「成長戦略」

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

This skill should be used when reviewing vendor estimates for software development projects. Use this skill when you need to evaluate whether a vendor's cost estimate, timeline, and approach are reasonable and whether the project is likely to succeed. This skill helps identify gaps, risks, overestimates, underestimates, and unfavorable contract terms. It generates comprehensive Markdown review reports with actionable recommendations to optimize costs while ensuring project success.

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