Kitt ↔ Hive integration: session-review → GH discussion → hive dispatch → agent analysis

[bacleclement]

RICE Score: 1.1 (Rank #10)

Reach	Impact	Confidence	Effort
3	3 (massive)	50%	4d

Problem

Kitt and Hive are disconnected systems. Session reviews stay local. Hive agents (CTO, QA Lead, Obs Chief, etc.) could analyze aggregated development patterns across sessions and projects — but they have no feed.

Vision

session-review completes
  ↓
strips sensitive data (no code, no credentials, no names, no IP)
  ↓
posts anonymized process metrics to kitt GH Discussion
  ↓
hive dispatcher reads new discussions (scheduled or webhook)
  ↓
routes to relevant agent:
  - CTO → architecture patterns, tech debt signals
  - QA Lead → test coverage trends, recurring failures
  - Scrum Master → velocity trends, spec quality scores
  - Product Chief → feature completion patterns
  ↓
agents produce recommendations back to the discussion

What Gets Shared (anonymized)

{
  "project_id": "hash",
  "work_type": "feature",
  "size": "M",
  "metrics": {
    "total_duration_min": 145,
    "skills_used": ["refine", "build-plan", "implement", "code-review"],
    "feedback_count": 3,
    "spec_drift_score": 4,
    "verify_first_pass_rate": 0.85,
    "debug_triggers": 1,
    "tokens_total": 210000,
    "cost_estimate": 0.85
  },
  "improvements": [
    { "type": "context-stale", "detail": "agent doc 37 days old" },
    { "type": "spec-quality", "detail": "5 corrections, 3 about edge cases" }
  ]
}

What Is NEVER Shared

• Source code or diffs
• File paths or project structure
• Ticket titles, descriptions, or IDs
• User names, emails, or identifiers
• Company or repo names
• Business domain details

Prerequisites

1. Session-review must be stable (Session-review: include user feedback content + token usage tracking #3, Session-review: generate actionable improvement tickets (kitt/context/PM quality) #4)
2. GH Discussions must be enabled on kitt repo
3. Hive dispatcher needs a "read GH discussions" trigger
4. Privacy review of anonymization logic

Batch

Batch D — Roadmap (high architectural impact, requires stability of earlier features)