abdulkerimatik/ OobeyaAnalytics:latest

15 2 months ago

Oobeya AI Development Productivity Analytics Assistant

tools thinking 
ollama run abdulkerimatik/OobeyaAnalytics

Details

2 months ago

5b9e4e4f2415 · 5.2GB ·

model
qwen3
·
8.19B
·
Q4_K_M
license
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR US
system
You are an expert Oobeya AI assistant specializing in software development productivity analysis. Yo
params
{ "repeat_penalty": 1, "stop": [ "<|im_start|>", "<|im_end|>" ], "te
template
{{- $lastUserIdx := -1 -}} {{- range $idx, $msg := .Messages -}} {{- if eq $msg.Role "user" }}{{ $la

Readme

Oobeya AI Development Productivity Analytics Assistant

Purpose

A specialized AI assistant that analyzes software development productivity metrics and generates executive-ready insights for engineering leaders, CTOs, and development team managers.

Core Capabilities

  • Development Metrics Analysis: Interprets cycle times, deployment frequency, lead times, throughput, and other DORA/SPACE framework metrics
  • Trend Identification: Detects patterns, anomalies, and performance shifts in engineering productivity data
  • Executive Reporting: Produces concise, data-driven insights formatted for leadership consumption
  • Team Performance Assessment: Evaluates developer efficiency, collaboration patterns, and delivery velocity

Strict Operational Boundaries

ONLY performs: Analysis of provided development productivity metrics NEVER performs: Code writing, debugging, architecture design, implementation tasks, or general software development assistance

Key Differentiators

  • Zero hallucination policy: Only references explicitly provided metrics; never invents data or applies assumed benchmarks
  • Strict scope enforcement: Immediately rejects out-of-domain requests with standardized refusal message
  • Data integrity focus: Explicitly flags missing data and analysis limitations rather than filling gaps with assumptions
  • Structured output format: Delivers insights in four distinct sections separated by ###NEXT_SECTION### markers

Ideal Use Cases

  • Reviewing sprint retrospective data
  • Analyzing quarterly engineering performance reports
  • Identifying bottlenecks in development pipelines
  • Comparing team productivity across periods
  • Generating board-level engineering health summaries

Target Users

Engineering executives, development managers, and technical leaders requiring objective, metric-based analysis of their teams’ productivity without implementation assistance.