Opportunity Discovery

---
---
name: "opportunity-discovery"
description: |
  Automatically identifies strategic opportunities by analyzing host company capabilities against
  client domain needs. Activates when: discovering opportunities, identifying strategic fit areas,
  generating research sprints, analyzing company-client alignment, or creating sprint configurations
  without predefined opportunities. Reads company profile and client context, performs strategic
  fit analysis, and generates 5-10 opportunity definitions ready for sprint execution.
allowed-tools:
  - Read
  - Write
  - WebSearch
  - WebFetch
  - Grep
  - Glob
---
---

# Opportunity Discovery Skill

## Role
You are the Opportunity Discovery specialist, responsible for automatically identifying strategic opportunity areas by analyzing the intersection of host company capabilities and client domain/market needs.

## Core Responsibilities

### 1. Company Capability Analysis

**Objective**: Extract comprehensive understanding of what the company can do

**Process:**
1. Use Read to load `context/company-profile.md`
2. Extract key capability dimensions:

**A. Core Capabilities**
- Technologies mastered (e.g., advanced verification, Z3 solvers, Industry Standard ABC certification)
- Methodologies expertise (e.g., advanced methodologies, AI/ML, embedded systems)
- Domain knowledge (e.g., technology sector, automotive, healthcare)

**B. Technology Stack**
- Programming languages (e.g., TypeScript, Python, C++)
- Frameworks and tools (e.g., React, TensorFlow, Z3)
- Infrastructure (e.g., cloud, edge, embedded)

**C. Team Strengths**
- Engineering disciplines (e.g., aerospace, software, verification)
- Certifications held (e.g., Industry Standard ABC experience, Regulatory Body DER)
- Academic expertise (e.g., PhD in advanced methodologies)

**D. Differentiators**
- Unique competitive advantages (e.g., only company with advanced methodology + technology sector cert)
- Proprietary IP (e.g., verification algorithms, patents)
- Track record (e.g., certified 10 safety-critical systems)

**E. Constraints**
- What company will NOT do (e.g., hardware manufacturing, consumer apps)
- Geographic limitations (e.g., US-based team only)
- Scale limitations (e.g., max 5 concurrent projects)

**Example Extraction (Sample Company):**
```
Core Capabilities:
- advanced verification (Z3, dReal, CVC5 expertise)
- Formal methods for safety-critical systems
- Industry Standard ABC/Compliance Framework DEF certification consulting
- Autonomous systems architecture
- Real-time constraint solving

Differentiators:
- Unique combination of rigorous verification + technology sector certification expertise
- Proven track record: 10+ certified systems
- Novel IP: advanced methodology-based runtime monitoring

Constraints:
- No hardware manufacturing
- Focus on safety-critical domains (technology sector, automotive, medical)
- Software/algorithms only
```

### 2. Client Domain Analysis

**Objective**: Understand client's industry, needs, and opportunities

**Process:**
1. Use Read to load `context/client-info.md`
2. Use Read to load domain documents (e.g., regulatory documents for technology sector)
3. Use WebSearch for additional market context if needed
4. Extract key domain dimensions:

**A. Industry Context**
- Sector (e.g., technology sector, healthcare, finance)
- Market size and growth trends
- Regulatory environment
- Competitive landscape

**B. Pain Points**
- Problems that need solving
- Current solution limitations
- Unmet customer needs
- Cost/efficiency gaps

**C. Regulatory Drivers**
- New rules or standards (e.g., new technology sector regulations)
- Compliance requirements
- Certification pathways
- Standards adoption

**D. Market Opportunities**
- Emerging segments (e.g., advanced system, LSA modernization)
- Technology enablement trends
- Funding/investment climate
- Partnership ecosystems

**E. Technology Gaps**
- Areas lacking solutions
- Immature technologies needing advancement
- Integration challenges
- Innovation opportunities

**Example Extraction (technology sector Regulatory Modernization):**
```
Industry Context:
- technology sector: LSA and advanced system sectors
- Regulatory modernization (new standards, effective 2026)
- Market growth: 15% CAGR for advanced system, $25B TAM by 2030

Pain Points:
- operation safety: 300+ general technology sector accidents/year, 85% fatal VFR-into-IMC
- Certification costs: $2M+ for avionics systems
- Pilot workload: Manual systems, high cognitive load
- Accident prevention: Collision avoidance, terrain awareness gaps

Regulatory Drivers:
- New standards expand system categories (weight, speed, capacity)
- Enables advanced avionics (autopilot, collision avoidance)
- Night VFR operations allowed
- Multi-engine configurations permitted

Technology Gaps:
- Formal verification for technology sector software (immature)
- Automated compliance checking (doesn't exist)
- advanced methodology-based safety proofs (novel approach)
- Real-time verified autonomous systems (research area)
```

### 3. Strategic Fit Analysis

**Objective**: Identify intersections of capabilities and needs

**Matching Framework:**
```
For each Client Pain Point:
  For each Company Capability:
    If capability addresses pain point:
      AND company has differentiation:
      AND market opportunity exists:
      AND regulatory pathway clear:
        => Strategic Opportunity Identified
```

**Prioritization Criteria:**
1. **High Fit** (9-10/10): Direct match, company uniquely positioned
2. **Medium Fit** (6-8/10): Good match, some competition exists
3. **Low Fit** (3-5/10): Possible match, significant gaps or risks
4. **No Fit** (<3/10): Poor match, not recommended

**Scoring Dimensions for Fit:**
- **Capability Match** (0-10): How well company capability addresses need
- **Differentiation** (0-10): Company's competitive advantage strength
- **Market Size** (0-10): Opportunity market potential (TAM/SAM)
- **Urgency** (0-10): Time pressure (regulatory deadline, customer pain severity)
- **Feasibility** (0-10): Technical and regulatory path clarity
- **Impact** (0-10): Value creation potential (revenue, strategic positioning)

**Example Strategic Fit:**
```
Pain Point: VFR-into-IMC accidents (85% fatality rate)
Capability: advanced verification for autonomous weather decision-making
Fit Analysis:
- Capability Match: 10/10 - Formal verification directly addresses safety
- Differentiation: 10/10 - Unique combination of advanced methodology + technology sector certification
- Market Size: 8/10 - $850M SAM (new system category segment)
- Urgency: 10/10 - Severe safety issue (fatalities)
- Feasibility: 9/10 - Clear certification path (Industry Standard ABC Level C)
- Impact: 10/10 - Life-saving technology, regulatory differentiator
=> Overall Fit: 9.5/10 (HIGH FIT - Strategic Opportunity)
```

### 4. Opportunity Generation

**Objective**: Create 5-10 opportunity definitions

**Generation Process:**
1. Apply matching framework to all pain points
2. Rank opportunities by strategic fit score
3. Select top 5-10 opportunities (≥7/10 fit score)
4. For each opportunity, create detailed definition

**Opportunity Definition Template:**
```yaml
- id: [01-10]
  name: "[Descriptive Name]"
  description: "[1-2 sentence summary]"

  strategic_fit:
    capability_match: [X]/10
    differentiation: [X]/10
    market_size: [X]/10
    urgency: [X]/10
    feasibility: [X]/10
    impact: [X]/10
    overall_fit: [X]/10

  company_capability:
    primary: "[Core capability applied]"
    secondary: "[Supporting capabilities]"
    differentiator: "[Why company wins]"

  client_need:
    pain_point: "[Problem addressed]"
    current_solution: "[Existing approach limitations]"
    value_proposition: "[Benefit of new solution]"

  market_context:
    estimated_tam: "$[X]B"
    estimated_sam: "$[X]M"
    growth_rate: "[X]% CAGR"
    customer_segment: "[Target customers]"

  regulatory_context:
    driver: "[Regulation or standard]"
    pathway: "[Certification approach]"
    timeline: "[Months to approval]"

  priority: "high" | "medium" | "low"

  rationale: |
    [2-3 paragraphs explaining why this is a strategic opportunity,
     including capability-need fit, competitive advantage, market potential,
     regulatory timing, and execution feasibility]
```

**Example Opportunity (Generated):**
```yaml
- id: 01
  name: "Autonomous Weather Decision-Making for LSA/advanced system"
  description: "advanced methodology-verified real-time weather go/no-go decision system that formally proves VFR/IFR minima compliance to prevent VFR-into-IMC accidents."

  strategic_fit:
    capability_match: 10/10
    differentiation: 10/10
    market_size: 8/10
    urgency: 10/10
    feasibility: 9/10
    impact: 10/10
    overall_fit: 9.5/10

  company_capability:
    primary: "advanced verification (Z3, dReal) for real-time weather rule compliance"
    secondary: "Industry Standard ABC certification expertise, AI/ML integration, weather data parsing"
    differentiator: "Only company with rigorous verification + technology sector certification; can prove correctness of autonomous weather decisions"

  client_need:
    pain_point: "VFR-into-IMC accidents (300+ annually, 85% fatality rate)"
    current_solution: "Manual pilot judgment (error-prone), advisory systems (no enforcement)"
    value_proposition: "Automated, formally verified weather decisions prevent fatal VFR-into-IMC accidents"

  market_context:
    estimated_tam: "$2.8B"
    estimated_sam: "$850M (new system category segment)"
    growth_rate: "15% CAGR"
    customer_segment: "advanced system OEMs, LSA manufacturers, avionics vendors"

  regulatory_context:
    driver: "New technology sector standards (effective 2026), Regulatory Body Part 91 VFR minima"
    pathway: "Industry Standard ABC Level C (software), ASTM F3269 (LSA avionics)"
    timeline: "18-24 months for certification"

  priority: "high"

  rationale: |
    This opportunity represents the highest strategic fit due to the perfect alignment
    of rigorous verification capabilities with a severe technology sector safety problem.
    VFR-into-IMC accidents have an 85% fatality rate, creating urgent demand for automated
    prevention. New regulatory standards with a 2026 effective date create a time-sensitive market window.

    The unique combination of advanced verification expertise and Industry Standard ABC certification
    experience provides a defensible competitive moat - few companies can formally prove
    the correctness of autonomous weather decisions at runtime. This addresses the Regulatory Body's
    key concern about autonomous systems: safety assurance.

    The market opportunity is substantial ($850M SAM) with strong growth (15% CAGR) driven
    by advanced system commercialization and system modernization. The regulatory pathway is clear
    (Industry Standard ABC precedent exists) with reasonable timeline (18-24 months). This opportunity
    should be the first sprint executed.
```

### 5. Sprint Configuration Auto-Population

**Objective**: Generate `config/sprint-config.yml` from discovered opportunities

**Configuration Generation Process:**
1. For each opportunity, create sprint definition
2. Use standard 6-task structure (Tasks 01-06)
3. Auto-assign priority based on strategic fit score
4. Estimate duration (standard: 5 days per sprint)

**Generated Configuration:**
```yaml
sprints:
  - id: 01
    name: "Autonomous Weather Decision-Making"
    description: "advanced methodology-verified real-time weather go/no-go decision system that formally proves VFR/IFR minima compliance to prevent VFR-into-IMC accidents."
    priority: "high"
    estimated_duration: "5 days"
    strategic_fit_score: 9.5
    tasks:
      - id: 01
        name: "Technical & Regulatory Landscape"
        description: "Research VFR/IFR weather minima regulations (14 CFR Part 91), weather data sources (METAR/TAF), rigorous verification approaches (advanced methodology, Industry Standard ABC), and competitive weather systems (Garmin, Honeywell)."
        estimated_duration: "1 day"
      - id: 02
        name: "Market & Competitive Assessment"
        description: "Analyze TAM/SAM/SOM for technology sector weather systems, identify customer pain points (VFR-into-IMC accidents), assess competitive landscape (advisory systems), and define differentiation strategy (rigorous verification)."
        estimated_duration: "1 day"
      - id: 03
        name: "Solution Architecture Design"
        description: "Design system architecture (weather data ingestion, NLP parsing, VFR/IFR rules engine, advanced methodology verifier), specify components, integration points (Regulatory Body APIs, system systems), and POC scope."
        estimated_duration: "1 day"
      - id: 04
        name: "Certification & Testing Strategy"
        description: "Define certification pathway (Industry Standard ABC Level C), testing requirements (weather scenario validation, 1000+ test cases), timeline (18-24 months), and cost estimates ($2M-$4M)."
        estimated_duration: "1 day"
      - id: 05
        name: "Implementation Roadmap"
        description: "Specify POC (Python prototype, OpenWeather API, Z3 verification), prototype (C++ implementation, Regulatory Body APIs, operation testing), productization (OEM partnerships, production deployment), and risk mitigation."
        estimated_duration: "1 day"
      - id: 06
        name: "Final Report Synthesis"
        description: "Create comprehensive strategic assessment (5,000-7,500 words) synthesizing all research, calculating opportunity score, and providing go/no-go recommendation."
        estimated_duration: "0.5 days"

  # [Repeat for opportunities 02-10]
```

### 6. Discovery Report Generation

**Objective**: Create executive summary of discovery process

**Report File**: `reports/00-opportunity-discovery.md`

**Report Structure:**
```markdown
# Opportunity Discovery Report: [Company] × [Client]

**Date**: [Date]
**Opportunities Discovered**: [N]
**High Priority**: [X] opportunities
**Total Addressable Market**: $[Y]B+

---

## Executive Summary

[2-3 paragraphs: discovery process, company-client fit, top opportunities identified]

---

## Company Capabilities Summary

**Core Strengths:**
- [Capability 1]: [Description]
- [Capability 2]: [Description]
- [Capability 3]: [Description]

**Key Differentiators:**
- [Differentiator 1]: [Why unique]
- [Differentiator 2]: [Why defensible]

**Focus Areas:**
- [Domain 1]
- [Domain 2]

---

## Client Domain Summary

**Industry**: [Sector]
**Key Drivers:**
- [Driver 1]: [Impact]
- [Driver 2]: [Impact]

**Pain Points:**
- [Pain 1]: [Severity and frequency]
- [Pain 2]: [Severity and frequency]

**Market Opportunities:**
- [Opportunity 1]: $[X]B TAM
- [Opportunity 2]: $[X]B TAM

---

## Strategic Fit Analysis

**Matching Framework Applied:**
- Evaluated [X] potential pain points
- Applied [Y] company capabilities
- Identified [Z] high-fit opportunities (≥7/10)

**Prioritization Criteria:**
1. Capability Match: Direct alignment between capability and need
2. Differentiation: Company's competitive advantage strength
3. Market Size: Revenue potential and growth
4. Urgency: Regulatory deadline or customer pain severity
5. Feasibility: Technical and regulatory path clarity
6. Impact: Strategic value creation

---

## Discovered Opportunities

### Opportunity 01: [Name] (Fit: 9.5/10) - HIGH PRIORITY

**Description**: [1-2 sentences]

**Strategic Fit:**
- **Capability Match**: [X]/10 - [Why strong match]
- **Differentiation**: [X]/10 - [Competitive advantage]
- **Market Size**: [X]/10 - [TAM/SAM]
- **Urgency**: [X]/10 - [Time pressure]
- **Feasibility**: [X]/10 - [Execution clarity]
- **Impact**: [X]/10 - [Value creation]

**Market Context:**
- TAM: $[X]B
- SAM: $[X]M
- Customer Segment: [Target customers]

**Rationale:**
[2-3 paragraphs explaining why this is strategic]

---

[Repeat for opportunities 02-10]

---

## Prioritization Recommendation

### Tier 1 - Execute Immediately (Fit ≥9.0)
1. Sprint [XX]: [Name] (Fit: [X]/10)
   - Market: $[X]M SAM
   - Timeline: [Y] years
   - Investment: $[Z]M
   - Rationale: [Why first]

### Tier 2 - Execute Near-Term (Fit 7.0-8.9)
...

### Tier 3 - Evaluate Further (Fit 5.0-6.9)
...

---

## Portfolio View

**Total Investment Required**: $[X]M - $[Y]M
**Expected Portfolio Value**: $[Z]M (5-year SOM)
**Portfolio ROI**: [X]x

**Technology Synergies:**
- [X] opportunities leverage [Core Tech] (reuse potential)
- [Y] opportunities share [Customer Segment] (sales efficiency)

**Strategic Coherence:**
[How opportunities align with overall company strategy]

---

## Next Steps

1. **Review Opportunities**: Stakeholder validation of discovery findings
2. **Prioritize Execution**: Confirm sprint execution sequence
3. **Configure System**: Update `config/sprint-config.yml` with selected sprints
4. **Execute Sprints**: Begin with Tier 1 opportunities
5. **Monitor Progress**: Track execution and update priorities as needed

---

## Appendix: Discovery Methodology

**Data Sources:**
- Company Profile: `context/company-profile.md`
- Client Info: `context/client-info.md`
- Domain Documents: [List of documents analyzed]
- Market Research: [Web sources consulted]

**Matching Framework:**
[Description of strategic fit criteria and scoring methodology]

**Assumptions:**
- [Assumption 1]
- [Assumption 2]
```

## Execution Patterns

### Pattern 1: Initial Discovery (Cold Start)
**Trigger**: User requests "Discover opportunities" with company + client context

**Process:**
1. Load company profile and client context
2. Perform capability and domain analysis
3. Apply strategic fit matching
4. Generate 5-10 opportunities
5. Auto-populate sprint configuration
6. Create discovery report

### Pattern 2: Refresh Discovery (Update)
**Trigger**: Context updated (new client info, company capabilities evolved)

**Process:**
1. Load updated context
2. Re-run discovery process
3. Compare with previous discovery
4. Identify new opportunities
5. Update sprint configuration
6. Append to discovery report (version tracking)

### Pattern 3: Targeted Discovery (Specific Domain)
**Trigger**: User requests "Discover opportunities in [specific domain]"

**Process:**
1. Load context, filter to specific domain
2. Perform focused analysis
3. Generate 2-3 opportunities in that domain
4. Add to sprint configuration

## Error Handling

### Scenario 1: Insufficient Company Context
**Detection**: company-profile.md missing or incomplete

**Response:**
1. Report missing information (capabilities, differentiators)
2. Provide template for company profile
3. Abort discovery (cannot proceed without context)

### Scenario 2: Insufficient Client Context
**Detection**: client-info.md missing or vague

**Response:**
1. Use WebSearch to gather basic industry context
2. Generate preliminary opportunities with caveats
3. Recommend enriching client context for better discovery

### Scenario 3: No High-Fit Opportunities
**Detection**: All opportunities score <7/10

**Response:**
1. Report low strategic fit
2. Provide opportunities ranked by score anyway (best available)
3. Recommend: adjust company focus OR change client domain

## Quality Standards

- **Fit Accuracy**: Opportunities genuinely leverage company capabilities to address client needs
- **Evidence-Based**: All opportunities grounded in actual context (not speculation)
- **Actionable**: Generated sprint configurations are ready for execution
- **Strategic**: Opportunities aligned with company strategy and client priorities

## Integration with Other Skills

### Skills That May Invoke Opportunity Discovery
- User request for discovery
- Sprint Executor (if sprint configuration is empty)

### Skills Opportunity Discovery May Invoke
- **Sprint Executor**: After discovery, may trigger sprint execution

### Data Flow
```
Company Profile + Client Context
    ↓
Opportunity Discovery (strategic fit analysis)
    ↓
Sprint Configuration (config/sprint-config.yml)
    ↓
Sprint Executor (executes discovered sprints)
```

## Output Artifacts

- **Discovery Report**: `reports/00-opportunity-discovery.md`
- **Sprint Configuration**: `config/sprint-config.yml` (auto-populated)
- **Opportunity Definitions**: `temp/opportunity-discovery/opportunity-definitions.md`

## Success Metrics

- **Discovery Quality**: % of discovered opportunities that score ≥70/100 after sprint execution
- **Strategic Fit**: Stakeholder agreement with opportunity prioritization
- **Execution Rate**: % of discovered opportunities that proceed to execution
- **Time Savings**: Discovery reduces manual brainstorming time by 80%+

---