Godiva LD Reference

Map system outages to LaunchDarkly bundles and associated FE flags.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/myriosMin/godiva --skill godiva-ld-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Godiva LD Reference
Source: https://github.com/myriosMin/godiva/tree/main/claude-managed-agents/skills/godiva-ld-reference
Command: npx skills add https://github.com/myriosMin/godiva --skill godiva-ld-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authoritative lookup for LaunchDarkly bundles to manage feature flags during Godiva incident response, reducing confusion and misconfiguration.

Core Features & Use Cases

  • Bundle lookup by Domain or Function to determine the correct LD Bundle Name.
  • Toggle all FE flags associated with a bundle simultaneously to ensure consistent user experience during outages.
  • Severity-aware guidance for approval workflows and incident response coordination.

Quick Start

Identify the outage domain or function, locate the matching LaunchDarkly bundle in this reference, then apply the associated FE flags to activate the correct feature set.

Frequently Asked Questions about Godiva LD Reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map LaunchDarkly bundles to frontend flags during an incident response?

A LaunchDarkly bundle maps to a specific set of frontend flags to ensure consistent user experience during outages. This reference provides structured mapping of bundles, dependencies, customer impact, and severity levels for synchronized flag toggling.

How do I toggle all frontend flags associated with a LaunchDarkly bundle?

To toggle all frontend flags associated with a bundle, look up the bundle by domain or function in the reference, then apply the mapped FE flags simultaneously to activate the correct feature set across the system.

Does LaunchDarkly incident response mapping require external dependencies or approval workflows?

LaunchDarkly incident response mapping requires no external dependencies beyond the reference data itself. It provides severity-aware guidance for approval workflows and incident response coordination across domain and function scopes.

What's the best way to identify the correct LaunchDarkly bundle for a system outage?

The best way to identify the correct LaunchDarkly bundle for a system outage is to search by the specific outage domain or function within the reference data, which then provides the corresponding LD bundle name and associated flags.

Can I use this LaunchDarkly bundle mapping for severity-based incident approvals across different domains?

Yes, you can use this bundle mapping across domain and function scopes for incident response. It enables synchronized flag toggling and includes severity-aware guidance specifically designed to streamline severity-based approval workflows.