netdata-config-from-requirements

What problem does it solve?

Producing correct Netdata OTLP and OpenTelemetry Collector configuration from a customer’s written requirements without direct access to their codebase or live infrastructure.

Core Features & Use Cases

• Requirements-to-bundle config generation: Extracts an atomic requirement inventory and converts it into a consistent folder deliverable containing YAML and a runbook the customer applies.
• Sane ambiguity handling: Converts missing or conflicting details into an open-questions.md manifest and prevents silent defaults by commenting unresolved knobs in otel.yaml.
• Skill composition for accuracy: Delegates receiver, Collector, instrumentation handoff, and migration decisions to the appropriate sibling skills while keeping bundle output in sync.

Quick Start

Ask an agent: "Given the following customer requirements text, generate a Netdata hand-off config bundle (otel.yaml, optional collector configs, per-language instrumentation handoff, open questions, and a customer-run verify.md) without guessing missing values and compose it using the sibling Netdata skills referenced in the rules."