engineering-operations-intelligencelisted

# Engineering Operations Intelligence ## Outcome Create one compact workflow that turns authorized engineering-system data into trusted team metrics, evidence-backed findings, recurring reviews, and tracked improvement actions. ## When to use Use when a small engineering team wants a shared view of delivery, quality, releases, and reliability without operating a separate data platform and review workflow. Start on demand and add ingestion triggers or a review schedule after the complete route succeeds. ## Discovery and user direction Inspect the current workflow, goals, metrics, configuration, capabilities, stores, reports, and triggers. Default to one workflow for one small team; split only for incompatible access or lifecycle boundaries. Summarize reuse and gaps, ask focused questions about unresolved scope, definitions, targets, ownership, cadence, and approvals, and record the answers. Installation is guidance, not approval. ## Required inputs Resolve team/repository/service scope, authorized sources, history and freshness, identity and workflow-state mappings, metric definitions and exclusions, goals or targets, review audience/cadence, action owners, retention, restricted fields, and approval/delivery policy. ## Plan and AgentWorks tools Use scripted steps to ingest and normalize source records, calculate reproducible metric snapshots, check data quality, freeze review periods, and persist reports. Use a message sequence to investigate supported changes and dr