인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
데이터 및 연구 · SKILL.md

strategy-frameworks

strategy-frameworks

Structure organizational strategy work: strategic direction, competitive and industry analysis, growth options, capital allocation, acquisitions, and portfolio choices. Use when framing consequential choices about where to compete, how to pursue an opportunity, or how to compare strategic options. Do not use this skill for unrelated requests; route to the n…

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: strategy-frameworks description: >- Structure organizational strategy work: strategic direction, competitive and industry analysis, growth options, capital allocation, acquisitions, and portfolio choices. Use when framing consequential choices about where to compete, how to pursue an opportunity, or how to compare strategic options. Do not use this skill for unrelated requests; route to the nearest named specialist. license: MIT metadata: source_repo: https://github.com/magnus919/hermes-profiles source_commit: 867a555 source_path: skills/strategy-frameworks

Strategy Frameworks

Use a framework to make assumptions, alternatives, evidence, and trade-offs visible. Select a reference for the decision at hand rather than applying every framework.

NeedLoad
Direction, OKRs, values, or a narrativereferences/strategic-planning.md
Industry structure, positioning, or potential advantagesreferences/competitive-analysis.md
Growth options, maturity states, or market entryreferences/growth-strategy.md
Capital choices, acquisitions, or a business portfolioreferences/resource-allocation.md
Provenance and catalog boundariesreferences/source-index.md

Working Method

  1. State the decision, decision owner, constraints, and evidence available.
  2. Use the relevant framework to generate questions and options, not a verdict.
  3. Record assumptions, uncertainties, trade-offs, and conditions that would change the recommendation.
  4. Pair strategic logic with appropriate financial, customer, technical, legal, or operational analysis.

When Not to Use

  • For stakeholder interviews and raw requirement discovery, use product-discovery.
  • For feature prioritization, specifications, and product communications, use product-methodology.
  • For quantitative scenarios, valuation, unit economics, or capital-model calculations, use financial-modeling.
  • For technology adoption posture and architecture governance, use technology-radar.

Completion

Stop when the artifact names the decision, alternatives, evidence, key assumptions, trade-offs, and next validation or decision step. It should not present a framework classification as a prediction or decision by itself.

저장한 Skills