This tool provides centralized control over plugin activation states for a content management system using configuration files. It is designed for developers and teams managing multiple environments (like development, staging, and production) who need consistent, version-controlled plugin setups.

• Configuration File Management: Uses JSON files placed in standard directories (like /wp-content or theme folders) to define lists of plugins to activate or deactivate. These configurations are merged from multiple sources, including from within plugins themselves to handle dependencies.
• Enforced Activation States: Supports forcing a plugin to be active or inactive, removing the ability for users to change its state from the admin interface or via command line. This ensures critical plugins remain in their required state.
• Custom Plugin Paths: Allows specifying plugins located outside the standard plugins directory by defining a custom file path and load priority, offering flexibility in project structure.
• Dynamic Control via Code: Enables programmatic modification of the plugin configuration using PHP hooks. This allows for environment-specific rules, such as activating a debug plugin only on a staging server.
• Command Line Interface: Includes WP-CLI commands to list all dictated plugins and their statuses, and to reset the site's plugins to match the configuration files, simplifying deployment and synchronization tasks.