[FEATURE] Plugin dynamic config input

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

We are working on a plugin that will be shared across various engineering teams at our company. The agents, commands and skills will be common across the different teams, each project will require specific values that are not shared. For example but not limited to:

• Jira Project Key
• Confluence Space Identifier
• Prompt hints tailored to each project's specific config

Proposed Solution

If there is a existing mewthod to achieve the above please let us know, otherwise I propose something such as passing configuration values to each enabled plugin via the project's settings.json.

{
  "extraKnownMarketplaces": {
    "XYZ-claude-marketplace": {
      "source": {
        "source": "url",
        "url": "https://github.com/XYZ/XYZ-claude-marketplace.git"
      }
    }
  },
  "enabledPlugins": {
    "frontend@XYZ-claude-marketplace": true, // Already exists
    "backend@XYZ-claude-marketplace": { // Proposed config
       "enabled": true,
       "env": {
         "JIRA_KEY": "PROJ",
         "SPACE_KEY": "SPACE",
         "PROMPT_HINT": "This project is a frontend app designed to....",
       }
     }
  }
}

It doesn't have to be exactly like above but the solution should allow a consumer of a plugin to pass values into it that the plugin might need some static input from the user|project.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

DRI Investigation Agent that has the ability to query a specific Azure Application Insights instance based on project and environment via MCP. The agent can check the JIRA ticket that contains the query that triggered the alert (via Atlassian MCP), figure out the possible cost and update the ticket.

All of the above is already functional for one project but to make it work for additional projects:

1. The Agent needs to know which App insights to use (currently env vars)
2. The agent needs to know the Atlassian details (current env vars)
3. The agent needs to have its prompts tweaked for every project as every project uses app insights differently

This is just one real example, we have other ideas that would require configuration.

Additional Context

_No response_