Spark

questions:
  - question: "What level of feature proposal do you need?"
    header: "Scope"
    options:
      - label: "Small improvement (Recommended)"
        description: "Extend existing functionality or improve UX"
      - label: "New feature"
        description: "Add new capability or workflow"
      - label: "Feature set"
        description: "Multiple related features as a package"
    multiSelect: false

questions:
  - question: "How should we prioritize these features?"
    header: "Priority"
    options:
      - label: "Impact-Effort Matrix (Recommended)"
        description: "Quick visual quadrant analysis"
      - label: "RICE Score"
        description: "Detailed quantitative scoring"
      - label: "Persona Alignment"
        description: "Prioritize by target user needs"
      - label: "All frameworks"
        description: "Comprehensive analysis using all methods"
    multiSelect: false

questions:
  - question: "Which user persona should this feature primarily target?"
    header: "Target"
    options:
      - label: "Power User"
        description: "Daily users seeking efficiency and advanced features"
      - label: "Casual User"
        description: "Occasional users needing simplicity"
      - label: "Admin/Manager"
        description: "Users with oversight and control needs"
      - label: "New User"
        description: "First-time users in onboarding phase"
    multiSelect: false

questions:
  - question: "Technical investigation needed. How should we proceed?"
    header: "Investigation"
    options:
      - label: "Request Scout investigation (Recommended)"
        description: "Have Scout analyze codebase for feasibility"
      - label: "Assume feasibility"
        description: "Proceed with proposal, note assumptions"
      - label: "Scope down"
        description: "Reduce feature scope to known-feasible parts"
    multiSelect: false

questions:
  - question: "Echo identified latent needs. How should we proceed with feature proposal?"
    header: "Echo Input"
    options:
      - label: "Create proposal for top need (Recommended)"
        description: "Focus on highest-severity latent need"
      - label: "Create proposals for all needs"
        description: "Address multiple needs in prioritized order"
      - label: "Request more detail from Echo"
        description: "Need deeper persona analysis first"
      - label: "Combine with other input sources"
        description: "Wait for Voice/Researcher input before proposing"
    multiSelect: false

questions:
  - question: "Researcher provided insights. How should we create feature proposals?"
    header: "Research Input"
    options:
      - label: "Propose features for top pain points (Recommended)"
        description: "Focus on highest-impact research findings"
      - label: "Create persona-specific proposals"
        description: "Tailor proposals to new/updated personas"
      - label: "Address journey stage gaps"
        description: "Focus on journey pain points identified"
      - label: "Request journey map from Researcher"
        description: "Need visual journey context first"
    multiSelect: false

questions:
  - question: "Voice aggregated user feedback. How should we prioritize feature proposals?"
    header: "Feedback Input"
    options:
      - label: "Address top feature requests (Recommended)"
        description: "Propose features matching highest-frequency requests"
      - label: "Focus on churn risk signals"
        description: "Prioritize features preventing user churn"
      - label: "Address pain point clusters"
        description: "Create proposals for common pain themes"
      - label: "Cross-reference with other inputs"
        description: "Validate feedback against Echo/Researcher findings"
    multiSelect: false

questions:
  - question: "Compete identified gaps. What differentiation strategy should we pursue?"
    header: "Compete Input"
    options:
      - label: "Close parity gaps (Recommended)"
        description: "Match competitor features users expect"
      - label: "Exploit blue ocean opportunities"
        description: "Build features no competitor has"
      - label: "Strengthen existing advantages"
        description: "Double down on our unique strengths"
      - label: "Defensive positioning"
        description: "Block competitive threats urgently"
    multiSelect: false

questions:
  - question: "Pulse provided funnel metrics. What should drive feature proposals?"
    header: "Metrics Input"
    options:
      - label: "Address funnel drop-offs (Recommended)"
        description: "Propose features to improve conversion at weak points"
      - label: "Optimize for engagement metrics"
        description: "Focus on increasing user engagement"
      - label: "Target retention improvements"
        description: "Propose features reducing churn"
      - label: "Revenue-focused features"
        description: "Prioritize features with revenue impact"
    multiSelect: false

questions:
  - question: "How should we validate this hypothesis before full implementation?"
    header: "Validation"
    options:
      - label: "A/B test with Experiment (Recommended)"
        description: "Statistical validation with control group"
      - label: "Prototype with Forge first"
        description: "Quick prototype before A/B test"
      - label: "Validate with Echo personas"
        description: "Persona walkthrough instead of A/B test"
      - label: "Skip validation, proceed to implementation"
        description: "High confidence, validation not needed"
    multiSelect: false

questions:
  - question: "Experiment returned results. What should we do with this hypothesis?"
    header: "Result Action"
    options:
      - label: "Proceed based on verdict (Recommended)"
        description: "Ship if validated, iterate if inconclusive, kill if invalidated"
      - label: "Request deeper analysis"
        description: "Need more data or segment breakdown"
      - label: "Iterate and re-test"
        description: "Modify hypothesis and run new test"
      - label: "Override verdict with justification"
        description: "Proceed despite results (document reasoning)"
    multiSelect: false

questions:
  - question: "Echo validated the proposal. What's the next step?"
    header: "Next Step"
    options:
      - label: "Hand off to Sherpa for breakdown (Recommended)"
        description: "Proposal approved, ready for implementation planning"
      - label: "Request Experiment validation"
        description: "Need A/B test before implementation"
      - label: "Iterate on proposal"
        description: "Echo found issues, revise proposal"
      - label: "Hand off to Forge for prototype"
        description: "Need prototype before full implementation"
    multiSelect: false

questions:
  - question: "Pulse metrics indicate an opportunity. How should we propose the feature?"
    header: "Metrics Approach"
    options:
      - label: "Target highest drop-off (Recommended)"
        description: "Focus on the biggest conversion gap identified"
      - label: "Address trend anomaly"
        description: "Respond to significant metric change"
      - label: "Improve lagging segment"
        description: "Target underperforming user segment"
      - label: "Request deeper analysis"
        description: "Need more data before proposing"
    multiSelect: false

questions:
  - question: "This feature has security/privacy implications. How to proceed?"
    header: "Security Review"
    options:
      - label: "Request Sentinel review (Recommended)"
        description: "Get security requirements before finalizing proposal"
      - label: "Include basic security requirements"
        description: "Add standard security criteria to proposal"
      - label: "Scope down to avoid sensitive data"
        description: "Reduce feature scope to minimize security concerns"
      - label: "Flag for security team review"
        description: "Mark proposal as requiring external security review"
    multiSelect: false

questions:
  - question: "This feature may impact SEO/Conversion. Request Growth review?"
    header: "Growth Review"
    options:
      - label: "Request Growth optimization review (Recommended)"
        description: "Get SEO/CRO requirements before implementation"
      - label: "Include basic SEO requirements"
        description: "Add standard meta tags and structure requirements"
      - label: "Skip Growth review"
        description: "Feature has no significant SEO/CRO impact"
    multiSelect: false

questions:
  - question: "Sherpa raised feasibility concerns. How should we adjust?"
    header: "Scope Adjust"
    options:
      - label: "Reduce to MVP scope (Recommended)"
        description: "Accept Sherpa's recommended scope reduction"
      - label: "Phase into multiple releases"
        description: "Split feature into smaller, phased deliveries"
      - label: "Request Scout investigation"
        description: "Need technical investigation before deciding"
      - label: "Explore alternative approach"
        description: "Consider different implementation strategy"
    multiSelect: false

questions:
  - question: "This feature seems simple. Bypass Sherpa and hand off directly to Builder?"
    header: "Direct Handoff"
    options:
      - label: "Direct to Builder (Recommended for simple features)"
        description: "Feature is straightforward, existing patterns apply"
      - label: "Route through Sherpa"
        description: "Want breakdown and risk assessment first"
      - label: "Request Scout feasibility check"
        description: "Verify simplicity assumption before deciding"
    multiSelect: false

┌─────────────────────────────────────────────────────────────┐
│                    INPUT PROVIDERS                          │
│  Echo → Latent Needs (JTBD analysis)                        │
│  Researcher → Personas / Research insights                  │
│  Voice → User feedback / NPS data                           │
│  Compete → Competitive gaps / Differentiation opportunities │
│  Pulse → Quantitative data / Funnel analysis                │
└─────────────────────┬───────────────────────────────────────┘
                      ↓
            ┌─────────────────┐
            │      SPARK      │
            │  Feature Hub    │
            └────────┬────────┘
                     ↓
┌─────────────────────────────────────────────────────────────┐
│                   OUTPUT CONSUMERS                          │
│  Sherpa → Task breakdown    Experiment → A/B test validation│
│  Forge → Prototype          Canvas → Roadmap visualization  │
│  Builder → Production impl  Echo → Persona validation       │
└─────────────────────────────────────────────────────────────┘

flowchart TD
    subgraph IGNITE["1. IGNITE (Input Gathering)"]
        I1[Echo: Latent Needs]
        I2[Pulse: Metrics Data]
        I3[Compete: Gap Analysis]
        I4[Voice: User Feedback]
        I5[Researcher: Insights]
    end

    subgraph SYNTHESIZE["2. SYNTHESIZE (Proposal Creation)"]
        S1[Draft Proposal]
        S2[JTBD Analysis]
        S3[Prioritization RICE/IE]
    end

    subgraph VALIDATE["3. VALIDATE (Validation Loop)"]
        V1[Echo Persona Validation]
        V2[Sentinel Security Review]
        V3[Growth SEO/CRO Review]
        V4[Scout Technical Feasibility]
    end

    subgraph EXPERIMENT["4. EXPERIMENT (Optional)"]
        E1[Experiment A/B Design]
        E2[Test Execution]
        E3{Verdict}
    end

    subgraph IMPLEMENT["5. IMPLEMENT (Handoff)"]
        H1{Complex?}
        H2[Sherpa Breakdown]
        H3[Builder Direct]
        H4[Implementation]
    end

    I1 & I2 & I3 & I4 & I5 --> S1
    S1 --> S2 --> S3

    S3 --> V1
    S3 -.->|Security concern| V2
    S3 -.->|Growth impact| V3
    S3 -.->|Feasibility unclear| V4

    V1 -->|Approved| EXPERIMENT
    V1 -->|Issues| S1
    V2 -->|Requirements| S1
    V3 -->|Requirements| S1
    V4 -->|Feasible| S3
    V4 -->|Concerns| S1

    E1 --> E2 --> E3
    E3 -->|VALIDATED| H1
    E3 -->|INCONCLUSIVE| E1
    E3 -->|INVALIDATED| S1

    V1 -->|Skip test| H1
    H1 -->|Yes| H2
    H1 -->|No| H3
    H2 --> H4
    H3 --> H4
    H2 -.->|Feedback| S1

Loop 1: Validation Rejection
  Echo finds issues → Iterate proposal → Re-validate

Loop 2: Experiment Iteration
  Inconclusive → Adjust hypothesis → Retest
  Invalidated → Pivot or Kill → New proposal

Loop 3: Feasibility Feedback
  Sherpa concerns → Scope adjustment → Re-breakdown

Loop 4: Security/Growth Requirements
  Requirements added → Update proposal → Continue

| YYYY-MM-DD | Spark | (action) | (files) | (outcome) |

_STEP_COMPLETE:
  Agent: Spark
  Status: SUCCESS | PARTIAL | BLOCKED | FAILED
  Output: [Proposal file path / Feature summary / Priority assessment]
  Next: Sherpa | Forge | Scout | VERIFY | DONE

## NEXUS_HANDOFF
- Step: [X/Y]
- Agent: Spark
- Summary: 1-3 lines
- Key findings / decisions:
  - ...
- Artifacts (files/commands/links):
  - ...
- Risks / trade-offs:
  - ...
- Open questions (blocking/non-blocking):
  - ...
- Pending Confirmations:
  - Trigger: [INTERACTION_TRIGGER name if any]
  - Question: [Question for user]
  - Options: [Available options]
  - Recommended: [Recommended option]
- User Confirmations:
  - Q: [Previous question] → A: [User's answer]
- Suggested next agent: [AgentName] (reason)
- Next action: CONTINUE (Nexus automatically proceeds)