> For the complete documentation index, see [llms.txt](https://help.sleuth.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sleuth.io/sleuth-dora/modeling-your-deployments/feature-flags.md). # Feature flags Feature flags are an integral part of agile software development, and an important variable in deploying a successful CI/CD pipeline. Making high-impact changes with minimal risk and maximum control of your applications helps deliver quality software to your customers. Sleuth integrates with your existing [LaunchDarkly](/sleuth-dora/integrations-1/feature-flags/launchdarkly.md) account to surface your feature flag changes within your Sleuth project. Setting up feature flags in Sleuth allows us to track and alert on flag changes via the same mechanisms used for your code deploys, providing you a single system of record for all your deploy changes. Sleuth allows a simple mapping between [LaunchDarkly environments](https://docs.launchdarkly.com/home/managing-flags/environments) and [Sleuth environments](/sleuth-dora/modeling-your-deployments/environment-support.md). Feature flag changes also trigger automatic health verification when you've setup Impact Sources. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.sleuth.io/sleuth-dora/modeling-your-deployments/feature-flags.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.