rootnode-domain-business-strategy
Specialized business strategy prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output formats) for consulting, M&A, corporate strategy, and strategic planning tasks. Use when building prompts for deal evaluation, due diligence, portfolio strategy, business model analysis, board narratives, investment cases, market entry plans, or strategic options assessments. Trigger on: "build a prompt for M&A analysis," "due diligence prompt," "board narrative," "investment case," "market entry strategy," "strategic options," "portfolio strategy prompt," "business model analysis prompt," "consulting-style analysis." Do NOT use for evaluating or scoring existing prompts (use rootnode-prompt-validation if available) or for auditing Claude Projects (use rootnode-project-audit if available).
rootnode · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add drayline/rootnode-skills --skill rootnode-domain-business-strategyAbout this skill
name: rootnode-domain-business-strategy description: >- Specialized business strategy prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output formats) for consulting, M&A, corporate strategy, and strategic planning tasks. Use when building prompts for deal evaluation, due diligence, portfolio strategy, business model analysis, board narratives, investment cases, market entry plans, or strategic options assessments. Trigger on: "build a prompt for M&A analysis," "due diligence prompt," "board narrative," "investment case," "market entry strategy," "strategic options," "portfolio strategy prompt," "business model analysis prompt," "consulting-style analysis." Do NOT use for evaluating or scoring existing prompts (use rootnode-prompt-validation if available) or for auditing Claude Projects (use rootnode-project-audit if available). license: Apache-2.0 metadata: author: rootnode version: "4.0.0" original-source: "DOMAIN_PACK_BUSINESS_STRATEGY.md"
Business Strategy Prompt Methodology
Calibration: Tier 1 (Model-compatible) - runs cleanly on the current dual-primary tier (Opus 5, Sonnet 5) as well as Haiku 4.5 with extended thinking. Structured retrieval, rule evaluation, or template lookup - output shape does not depend on model class. Correct-shape output also on Opus 4.8 (fallback-graceful) and Sonnet 4.6 (legacy-graceful). See repository README for model compatibility.
Specialized approaches for building Claude prompts that handle consulting, corporate strategy, M&A, and strategic planning work. This methodology provides identity approaches, reasoning methods, and output formats tuned for business strategy tasks that require deeper domain specialization than general-purpose strategic analysis.
Use these approaches when the task specifically requires consulting-style structured problem-solving, deal evaluation, portfolio management, business model mechanics, or strategy-specific deliverable formats.
How to Use This Skill
A well-structured Claude prompt for business strategy work uses up to four layers:
- Identity — Who Claude should be for this task (consulting, M&A, or corporate strategy perspective)
- Reasoning — How Claude should think through the problem (due diligence, business model analysis, portfolio strategy, or stakeholder dynamics)
- Output format — What the deliverable looks like (investment case, board narrative, market entry strategy, or strategic options assessment)
- Quality control — Verification instructions that catch common failure modes
Assemble the prompt by selecting one approach from each relevant layer, wrapping each in its XML tags (<role>, <reasoning>, <output_format>), and combining them with a <context> section containing the specific situation, data, and constraints.
Not every task needs all four layers. A quick strategic analysis may need only an identity and reasoning approach. A deliverable-focused task may need identity, output format, and a strong context section. Match the prompt's complexity to the task.
Approach Selection
Which Identity to Use
| Task Type | Identity Approach | Why |
|---|---|---|
| Structured problem decomposition, hypothesis-driven analysis, consulting deliverables | Management Consultant | Emphasizes analytical methodology and decision-ready output |
| Deal evaluation, acquisition analysis, merger assessment, partnership due diligence | M&A / Corporate Development Advisor | Integrates financial, strategic, and operational deal dimensions with skeptical-by-default stance |
| Internal strategic planning, portfolio decisions, cross-business-unit coordination | Corporate Strategist | Insider perspective that balances ambition with organizational reality |
| General strategic analysis not requiring domain specialization | Use a general Strategic Advisor approach — not in this Skill | General strategic work does not need domain-specific identity |
Which Reasoning Method to Use
| Task Type | Reasoning Method | Reference |
|---|---|---|
| Systematic evaluation of an acquisition, investment, or partnership | Due Diligence | See references/reasoning-approaches.md |
| Understanding how a business makes money — unit economics, cost structure, value chain | Business Model Analysis | See references/reasoning-approaches.md |
| Managing a portfolio of businesses, products, or investments — allocation, balance, composition | Portfolio Strategy | See references/reasoning-approaches.md |
| Navigating organizational politics, building support, managing resistance | Stakeholder & Organizational Dynamics | See references/reasoning-approaches.md |
Combining reasoning methods: For complex tasks, you can pair a primary reasoning method with a secondary one. Keep the total to 5-7 analytical steps — combining two full 6-step methods produces bloated, unfocused analysis. Lead with the dominant method and integrate elements of the secondary method where they add the most value. Stakeholder & Organizational Dynamics works especially well as a secondary method when any strategic initiative requires organizational buy-in.
Which Output Format to Use
| Deliverable Type | Output Format | Reference |
|---|---|---|
| Formal case for capital allocation or acquisition | Investment Case | See references/output-formats.md |
| Written narrative for a board of directors | Board Narrative | See references/output-formats.md |
| Plan for entering a new market, segment, or geography | Market Entry Strategy | See references/output-formats.md |
| Presenting and analyzing 2-3 distinct strategic paths | Strategic Options Assessment | See references/output-formats.md |
Quality Control for Business Strategy
When building business strategy prompts, add these task-specific quality checks after the output format section:
<quality_control>
Verify before delivering:
- Assumption transparency: Every financial proj
Read the complete source ↗