popilot 0.2.0

package/scaffold/.context/integrations/providers/ga4.yaml

@@ -0,0 +1,116 @@
+id: ga4
+name: "Google Analytics 4"
+category: analytics
+description: "Event-based user behavior analysis"
+
+mcp:
+  server_name: "ga4"
+  tools: [run_report, run_realtime_report]
+
+setup_questions:
+  - key: property_id
+    label: "GA4 Property ID"
+    type: string
+    required: true
+    example: "462897329"
+
+agent_prompts:
+  analyst: |
+    ### GA4 MCP
+
+    ```
+    Purpose: Event-based behavioral data analysis
+    property_id: {{config.property_id}}
+    ```
+
+    #### Common Patterns
+
+    **1. Cohort Retention (Monthly Signups)**
+    ```javascript
+    run_report({
+      property_id: "{{config.property_id}}",
+      date_ranges: [{ start_date: "90daysAgo", end_date: "yesterday" }],
+      dimensions: ["firstUserSourceMedium", "cohort", "cohortNthDay"],
+      metrics: ["cohortActiveUsers", "cohortTotalUsers"]
+    })
+    ```
+
+    **2. Segment-level Behavior Comparison**
+    ```javascript
+    run_report({
+      property_id: "{{config.property_id}}",
+      date_ranges: [{ start_date: "30daysAgo", end_date: "yesterday" }],
+      dimensions: ["userType", "pagePath"],
+      metrics: ["activeUsers", "screenPageViews", "averageSessionDuration"]
+    })
+    ```
+
+    **3. Anomaly Detection (Daily Trends)**
+    ```javascript
+    run_report({
+      property_id: "{{config.property_id}}",
+      date_ranges: [{ start_date: "30daysAgo", end_date: "yesterday" }],
+      dimensions: ["date"],
+      metrics: ["activeUsers", "newUsers", "eventCount"],
+      order_bys: [{ dimension: { dimension_name: "date" }, desc: false }]
+    })
+    ```
+
+  validator: |
+    ### GA4 MCP ⭐ Core Tool
+    ```
+    Purpose: Event data queries, funnel analysis, metric measurement
+    property_id: {{config.property_id}}
+    ```
+
+    #### Common Query Patterns
+
+    **1. Event Count Query**
+    ```javascript
+    run_report({
+      property_id: "{{config.property_id}}",
+      date_ranges: [{ start_date: "7daysAgo", end_date: "yesterday" }],
+      dimensions: ["eventName"],
+      metrics: ["eventCount"]
+    })
+    ```
+
+    **2. Funnel Analysis (By Page)**
+    ```javascript
+    run_report({
+      property_id: "{{config.property_id}}",
+      date_ranges: [{ start_date: "7daysAgo", end_date: "yesterday" }],
+      dimensions: ["pagePath"],
+      metrics: ["screenPageViews", "activeUsers"]
+    })
+    ```
+
+    **3. Specific Event Details**
+    ```javascript
+    run_report({
+      property_id: "{{config.property_id}}",
+      date_ranges: [{ start_date: "7daysAgo", end_date: "yesterday" }],
+      dimensions: ["eventName", "customEvent:campaign_id"],
+      metrics: ["eventCount"],
+      dimension_filter: {
+        filter: { field_name: "eventName", string_filter: { match_type: 1, value: "click_action_guide" }}
+      }
+    })
+    ```
+
+    **4. Daily Trends**
+    ```javascript
+    run_report({
+      property_id: "{{config.property_id}}",
+      date_ranges: [{ start_date: "14daysAgo", end_date: "yesterday" }],
+      dimensions: ["date", "eventName"],
+      metrics: ["eventCount"],
+      order_bys: [{ dimension: { dimension_name: "date" }, desc: false }]
+    })
+    ```
+
+command_prompts:
+  analytics: |
+    - **GA4 MCP Server** (Event data analysis)
+
+footer_tool_line: "GA4 MCP"

package/scaffold/.context/integrations/providers/intercom.yaml

@@ -0,0 +1,47 @@
+id: intercom
+name: "Intercom"
+category: customer_feedback
+description: "Customer support, messaging, VOC analysis"
+
+mcp:
+  server_name: "intercom"
+  tools: [list_conversations, get_conversation, search_contacts]
+
+setup_questions:
+  - key: app_id
+    label: "Intercom App ID"
+    type: string
+    required: true
+    example: "abc123"
+
+agent_prompts:
+  validator: |
+    ### Intercom API (VOC Analysis)
+    ```
+    Purpose: CS conversation analysis, VOC insight extraction
+    app_id: {{config.app_id}}
+    ```
+
+    #### VOC Analysis Patterns
+    ```javascript
+    // Retrieve recently closed conversations
+    list_conversations({
+      state: "closed",
+      per_page: 50,
+      sort_field: "updated_at",
+      sort_order: "desc"
+    })
+
+    // Retrieve specific conversation details
+    get_conversation({ id: "{conversation_id}" })
+    ```
+
+  researcher: |
+    ### Intercom API (VOC Collection)
+    ```
+    Purpose: Customer conversation collection, complaint pattern identification
+    app_id: {{config.app_id}}
+    Integration: Vicky collects → Rita interprets
+    ```
+
+footer_tool_line: "Intercom API"

package/scaffold/.context/integrations/providers/linear.yaml

@@ -0,0 +1,46 @@
+id: linear
+name: "Linear"
+category: pm_tool
+description: "Issue tracking, project management, roadmap"
+
+mcp:
+  server_name: "linear"
+  tools: [list_issues, create_issue, update_issue, list_projects]
+
+setup_questions:
+  - key: team_id
+    label: "Linear Team ID"
+    type: string
+    required: true
+    example: "TEAM-123"
+
+agent_prompts:
+  strategist: |
+    ### Linear MCP
+    ```
+    Purpose: Issue management, roadmap integration
+    team_id: {{config.team_id}}
+    Usage:
+    - list_issues: View issue list
+    - create_issue: Create new issue
+    - list_projects: View project status
+    ```
+
+  planner: |
+    ### Linear MCP
+    ```
+    Purpose: Sprint issue management, story creation
+    team_id: {{config.team_id}}
+    Usage:
+    - list_issues: View sprint issues
+    - create_issue: Create new issue
+    - update_issue: Update status
+    ```
+
+command_prompts:
+  daily: |
+    ### Linear Issue Sync
+
+    Automatically collects issues completed today from Linear and reflects them in the daily work log.
+
+footer_tool_line: "Linear MCP"

package/scaffold/.context/integrations/providers/mixpanel.yaml

@@ -0,0 +1,73 @@
+id: mixpanel
+name: "Mixpanel"
+category: analytics
+description: "Product analytics, funnels, retention"
+
+mcp:
+  server_name: "mixpanel"
+  tools: [query_jql, get_funnel, get_retention]
+
+setup_questions:
+  - key: project_id
+    label: "Mixpanel Project ID"
+    type: string
+    required: true
+    example: "2843271"
+  - key: api_secret
+    label: "Mixpanel API Secret (see secrets.yaml)"
+    type: string
+    required: false
+
+agent_prompts:
+  analyst: |
+    ### Mixpanel MCP
+    ```
+    Purpose: Product analytics, funnel analysis, retention analysis
+    project_id: {{config.project_id}}
+    ```
+
+    #### Common Patterns
+
+    **1. Event Trend Analysis**
+    ```javascript
+    query_jql({
+      project_id: "{{config.project_id}}",
+      from_date: "2026-02-01",
+      to_date: "2026-02-28",
+      event: "page_view"
+    })
+    ```
+
+    **2. Funnel Analysis**
+    ```javascript
+    get_funnel({
+      project_id: "{{config.project_id}}",
+      from_date: "2026-02-01",
+      to_date: "2026-02-28",
+      steps: ["sign_up", "onboarding_complete", "first_purchase"]
+    })
+    ```
+
+    **3. Retention Analysis**
+    ```javascript
+    get_retention({
+      project_id: "{{config.project_id}}",
+      from_date: "2026-01-01",
+      to_date: "2026-02-28",
+      born_event: "sign_up",
+      event: "page_view"
+    })
+    ```
+
+  validator: |
+    ### Mixpanel MCP
+    ```
+    Purpose: Hypothesis validation data queries, A/B test analysis
+    project_id: {{config.project_id}}
+    ```
+
+command_prompts:
+  analytics: |
+    - **Mixpanel MCP Server** (Product analytics, funnels, retention)
+
+footer_tool_line: "Mixpanel MCP"

package/scaffold/.context/integrations/providers/notebooklm.yaml

@@ -0,0 +1,74 @@
+id: notebooklm
+name: "NotebookLM"
+category: ai_research
+description: "AI-powered customer/user insight exploration"
+
+mcp:
+  server_name: "notebooklm"
+  tools: [ask_question, list_notebooks, select_notebook]
+
+setup_questions:
+  - key: notebook_name
+    label: "Active notebook name"
+    type: string
+    required: false
+    example: "my-notebook"
+
+agent_prompts:
+  researcher: |
+    ### NotebookLM MCP ⭐ Core Tool
+    ```
+    Purpose: Customer insights, interview data, domain knowledge
+    Active notebook: {{config.notebook_name}}
+    ```
+
+    #### Common Question Patterns
+
+    **1. Pain Point Discovery**
+    ```javascript
+    ask_question({
+      question: "What are the biggest pain points customers experience when using the service?",
+      session_id: "existing_session" // Maintain session
+    })
+    ```
+
+    **2. Needs Validation**
+    ```javascript
+    ask_question({
+      question: "Customers mentioned wanting a 'service that makes decisions for them' — what specific decisions do they want?",
+      session_id: "existing_session"
+    })
+    ```
+
+    **3. Workflow Understanding**
+    ```javascript
+    ask_question({
+      question: "In what order do customers use the key features, and what do they look at?",
+      session_id: "existing_session"
+    })
+    ```
+
+  strategist: |
+    ### NotebookLM MCP
+    ```
+    Purpose: Customer insights, market research
+    Active notebook: {{config.notebook_name}}
+    Usage:
+    - ask_question: Ask insight questions based on customer VOC
+    - Maintain sessions for in-depth exploration
+    ```
+
+    #### Usage Example
+    ```
+    🎯 Simon: "Let me check 'core feature improvement needs' on NotebookLM."
+    → ask_question({ question: "What are the most frequently mentioned pain points by customers regarding core features?" })
+    ```
+
+  validator: |
+    ### NotebookLM MCP
+    ```
+    Purpose: Customer insights, qualitative feedback analysis
+    Active notebook: {{config.notebook_name}}
+    ```
+
+footer_tool_line: "NotebookLM MCP"

package/scaffold/.context/integrations/providers/notion.yaml

@@ -0,0 +1,129 @@
+id: notion
+name: "Notion"
+category: pm_tool
+description: "Task management, document management, roadmap"
+
+mcp:
+  server_name: "notion"
+  tools: [notion-task-list, notion-task-create, notion-task-update, notion-task-update-status, notion-task-add-log, notion-task-my-sprint, notion-search, notion-fetch, notion-create-pages, notion-update-page]
+
+setup_questions:
+  - key: workspace
+    label: "Notion workspace name"
+    type: string
+    required: false
+    example: "My Workspace"
+  - key: daily_page_id
+    label: "Daily work log parent page ID"
+    type: string
+    required: false
+    example: "abc123..."
+
+agent_prompts:
+  strategist: |
+    ### Notion MCP
+    ```
+    Purpose: PRD lookup/creation, roadmap integration
+    Usage:
+    - notion-search: Search existing PRDs
+    - notion-fetch: Retrieve specific documents
+    - notion-create-pages: Create new PRDs
+    ```
+
+    #### Usage Example
+    ```
+    🎯 Simon: "Let me search for the competitive analysis document on Notion."
+    → notion-search({ query: "competitive analysis" })
+    ```
+
+  planner: |
+    ### Notion MCP
+    ```
+    Purpose: Sprint document management, story creation
+    Usage:
+    - notion-search: Search sprint documents
+    - notion-fetch: Retrieve specific stories
+    - notion-create-pages: Create new stories
+    - notion-update-page: Update progress status
+    ```
+
+    ### Usage Example
+    ```
+    📋 Penny: "Let me check the current sprint document."
+    → notion-fetch({ id: "Sprint-51-PRD-link" })
+
+    📋 Penny: "I'll create a new story."
+    → notion-create-pages({ parent: {page_id: "..."}, pages: [...] })
+    ```
+
+command_prompts:
+  daily: |
+    ### Notion Page Check and Creation
+
+    **Parent page**: `{{config.daily_page_id}}` (Daily work log)
+
+    1. Check if a child page with today's date title exists under the parent page
+    2. Create new if not found, update if exists
+
+    ### Notion Upload
+
+    ```javascript
+    mcp__notion__notion-create-pages({
+      parent: { page_id: "{{config.daily_page_id}}" },
+      pages: [{
+        properties: { title: "{YYYY-MM-DD}" },
+        content: "{formatted markdown}"
+      }]
+    })
+    ```
+
+workflow_rules:
+  - content: |
+      ## MCP Usage Guide
+
+      ### Notion MCP
+
+      You can manage tasks and view/create documents using Notion MCP.
+
+      | Tool | Purpose |
+      |------|---------|
+      | `notion-task-my-sprint` | View my sprint tasks |
+      | `notion-task-list` | View all task list |
+      | `notion-task-create` | Create new task |
+      | `notion-task-update` | Update task |
+      | `notion-task-update-status` | Change status only |
+      | `notion-task-add-log` | Add progress log |
+
+      User/Sprint mapping: See `.secrets.yaml`
+
+      ---
+
+      ## Story → Notion Task Upload
+
+      ### Overview
+
+      ```
+      spec-site (Source of Truth)    →    Notion (Execution Tracking)
+      Story Spec (Detailed Plan)      →    Task (Progress Management)
+      ```
+
+      ### Mapping Rules
+
+      | Story Section | Notion Task Section |
+      |---------------|---------------------|
+      | User Story | **Goal** (As a / I want / So that) |
+      | Acceptance Criteria (AC) | **Goal** (AC list summary) |
+      | Task Breakdown | **To-Do List** (checkboxes) |
+      | Expected Outcome | **Expected Outcome on Completion** |
+
+      ### Task Property Rules
+
+      | Property | Value | Example |
+      |----------|-------|---------|
+      | Title | `[Epic-Story] Title` | `[E-01-S-03] Dashboard Filtering` |
+      | Tags | Sprint, Epic, Area, Priority | `S52`, `E-02`, `FE`, `P1` |
+      | Assignee | `.secrets.yaml` userId | Assignee ID |
+      | Sprint | `.secrets.yaml` sprintId | Sprint page ID |
+      | Priority | P0→High, P1→Medium, P2→Low | `Medium` |
+
+footer_tool_line: "Notion MCP"

package/scaffold/.context/integrations/providers/prod_db.yaml

@@ -0,0 +1,183 @@
+id: prod_db
+name: "Production Database"
+category: database
+description: "Direct queries on production/snapshot DB"
+
+mcp:
+  server_name: "{{config.mcp_name}}"
+  tools: [query]
+
+setup_questions:
+  - key: mcp_name
+    label: "Production DB MCP server name"
+    type: string
+    required: true
+    example: "prod_service_db"
+  - key: snapshot_mcp_name
+    label: "Snapshot DB MCP server name"
+    type: string
+    required: false
+    example: "snapshot_service_db"
+  - key: tunnel_script
+    label: "Port forwarding/tunnel script path"
+    type: string
+    required: false
+    example: "bash scripts/port-forward.sh"
+  - key: caution
+    label: "Heavy table warning list (table name, risk level, reason)"
+    type: object_list
+    required: false
+    fields: [table, risk, reason]
+    example:
+      - table: SettlementMargin
+        risk: "🔴 Very High"
+        reason: "DELETE-INSERT ETL repeated, very heavy"
+  - key: rules
+    label: "DB usage rules summary"
+    type: string
+    required: false
+    example: "WHERE + indexed column + LIMIT required. Unconditional COUNT(*) prohibited"
+
+agent_prompts:
+  analyst: |
+    ### DB Selection Guide ⭐ Important
+
+    **Two databases are available:**
+
+    | DB | MCP Name | Port | Purpose | Data Point-in-Time |
+    |----|----------|------|---------|---------------------|
+    | **Snapshot DB** | `{{config.snapshot_mcp_name}}` | 33306 | General analysis, exploration | Early morning snapshot (previous day's closing data) |
+    | **Production DB** | `{{config.mcp_name}}` | 13306 | Only when real-time needed | Real-time |
+
+    #### 🎯 Selection Guide
+
+    ```
+    ✅ Use Snapshot DB (default, recommended)
+    - Cohort analysis, segment analysis
+    - Trend analysis (data up to yesterday)
+    - Exploratory analysis
+    - Heavy queries have no production impact
+
+    ⚠️ Use Production DB (only when needed)
+    - When "today's" data is absolutely required
+    - Real-time monitoring
+    - Debugging issues that occurred today
+    ```
+
+    #### 🔌 Port Forwarding Required Before DB Access
+
+    The tunneling script must be **run in a separate terminal first**:
+
+    ```bash
+    # Run the script within the project (opens 3 tunnels simultaneously)
+    {{config.tunnel_script}}
+    ```
+
+    Ports opened after execution:
+    | Environment | DB | Local Port |
+    |-------------|-----|-----------|
+    | Production | Service DB | `13306` |
+    | Production | Scrap DB | `23306` |
+    | Test | Service DB (Snapshot) | `33306` |
+
+    > **Note**: DB queries must be executed while the port forwarding session is already open.
+    > To terminate: `Ctrl+C`
+
+    #### ⚠️ Important: Heavy Table Precautions
+
+    **The following tables require special care:**
+
+    | Table | Risk Level | Reason |
+    |-------|------------|--------|
+    {{#each config.caution}}
+    | `{{this.table}}` | {{this.risk}} | {{this.reason}} |
+    {{/each}}
+
+    **Prohibited:**
+    ```sql
+    {{#each config.caution}}
+    -- ❌ Absolutely prohibited: Full Table Scan
+    SELECT * FROM {{this.table}};
+    SELECT * FROM {{this.table}} WHERE name LIKE '%search_term%';
+    SELECT COUNT(*) FROM {{this.table}};  -- Unconditional count
+
+    -- ❌ Absolutely prohibited: Unindexed conditions
+    SELECT * FROM {{this.table}} WHERE some_unindexed_column = 'value';
+    {{/each}}
+    ```
+
+    **Safe query patterns:**
+    ```sql
+    -- ✅ Safe: Conditions on indexed columns (user_id, created_at, etc.)
+    SELECT * FROM [table]
+    WHERE user_id = 123
+      AND created_at >= '2026-01-01'
+    LIMIT 100;
+
+    -- ✅ Safe: Sampling
+    SELECT * FROM [table]
+    WHERE user_id = 123
+    ORDER BY created_at DESC
+    LIMIT 50;
+    ```
+
+    **Pre-query checklist:**
+    - [ ] Is there an indexed column in the WHERE clause?
+    - [ ] Is LIMIT applied?
+    - [ ] For risky tables, proceed with extra caution
+
+command_prompts:
+  analytics: |
+    - **Prod DB MCP Server** (Direct Service DB queries)
+
+    ### Port Forwarding Required Before DB Access
+
+    ```bash
+    {{{config.tunnel_script}}}
+    ```
+
+    > Connects via local ports.
+
+    ## DB Precautions
+
+    The tables below store ETL results with frequent DELETE-INSERT operations and are **very heavy**. Full scan absolutely prohibited!
+
+    | Table | Risk Level | Reason |
+    |-------|------------|--------|
+    {{#each config.caution}}
+    | `{{this.table}}` | {{this.risk}} | {{this.reason}} |
+    {{/each}}
+
+    **Safe query rules:**
+    - WHERE clause with indexed columns (user_id, created_at, etc.)
+    - LIMIT required
+    - Unconditional COUNT(*) prohibited
+
+safety_rules:
+  - content: |
+      ## DB Precautions
+
+      → See `operations.integrations.prod_db.caution` in `.context/project.yaml`
+
+workflow_rules:
+  - content: |
+      ## DB Usage Precautions
+
+      ### Heavy Table Warnings
+
+      | Table | Precautions |
+      |-------|-------------|
+      {{#each config.caution}}
+      | `{{this.table}}` | {{this.risk}} {{this.reason}} |
+      {{/each}}
+
+      **Rules:** {{config.rules}}
+
+caution_list: |
+  | Table | Risk Level | Reason |
+  |-------|------------|--------|
+  {{#each config.caution}}
+  | `{{this.table}}` | {{this.risk}} | {{this.reason}} |
+  {{/each}}
+
+footer_tool_line: "Snapshot DB MCP (`{{config.snapshot_mcp_name}}`), Production DB MCP (`{{config.mcp_name}}`)"