opencastle 0.5.1 → 0.7.0

package/src/orchestrator/plugins/convex/config.ts

@@ -0,0 +1,33 @@
+import type { PluginConfig } from '../types.js';
+
+export const config: PluginConfig = {
+  id: 'convex',
+  name: 'Convex',
+  category: 'tech',
+  subCategory: 'database',
+  label: 'Convex',
+  hint: 'Reactive backend with real-time sync',
+  skillName: 'convex-database',
+  mcpServerKey: 'Convex',
+  mcpConfig: {
+    type: 'stdio',
+    command: 'npx',
+    args: ['-y', 'convex@latest', 'mcp', 'start'],
+  },
+  authType: 'none',
+  envVars: [],
+  agentToolMap: {
+    'database-engineer': [
+      'convex/status', 'convex/data', 'convex/tables', 'convex/functionSpec',
+      'convex/run', 'convex/envList', 'convex/envGet', 'convex/envSet',
+      'convex/envRemove', 'convex/runOneoffQuery', 'convex/logs', 'convex/insights',
+    ],
+    'security-expert': [
+      'convex/status', 'convex/tables', 'convex/functionSpec',
+      'convex/envList', 'convex/envGet', 'convex/logs', 'convex/insights',
+    ],
+  },
+  docsUrl: null,
+  officialDocs: 'https://docs.convex.dev/',
+  mcpPackage: 'convex',
+};

package/src/orchestrator/plugins/index.ts

@@ -0,0 +1,85 @@
+import type { PluginConfig } from './types.js';
+import { config as sanity } from './sanity/config.js';
+import { config as contentful } from './contentful/config.js';
+import { config as strapi } from './strapi/config.js';
+import { config as supabase } from './supabase/config.js';
+import { config as convex } from './convex/config.js';
+import { config as vercel } from './vercel/config.js';
+import { config as nx } from './nx/config.js';
+import { config as linear } from './linear/config.js';
+import { config as jira } from './jira/config.js';
+import { config as slack } from './slack/config.js';
+import { config as teams } from './teams/config.js';
+import { config as chromeDevtools } from './chrome-devtools/config.js';
+
+export type { PluginConfig, McpServerConfig, McpInput, EnvVarRequirement } from './types.js';
+
+/** All registered plugins, keyed by ID. */
+export const PLUGINS: Record<string, PluginConfig> = {
+  sanity,
+  contentful,
+  strapi,
+  supabase,
+  convex,
+  vercel,
+  nx,
+  'chrome-devtools': chromeDevtools,
+  linear,
+  jira,
+  slack,
+  teams,
+};
+
+/** Tech tool plugins only. */
+export const TECH_PLUGINS = Object.values(PLUGINS).filter(
+  (p) => p.category === 'tech'
+);
+
+/** Team tool plugins only. */
+export const TEAM_PLUGINS = Object.values(PLUGINS).filter(
+  (p) => p.category === 'team'
+);
+
+/** CMS plugins (subset of tech). */
+export const CMS_PLUGINS = TECH_PLUGINS.filter(
+  (p) => p.subCategory === 'cms'
+);
+
+/** Database plugins (subset of tech). */
+export const DB_PLUGINS = TECH_PLUGINS.filter(
+  (p) => p.subCategory === 'database'
+);
+
+/** Get a plugin by ID. */
+export function getPlugin(id: string): PluginConfig | undefined {
+  return PLUGINS[id];
+}
+
+/** Get all plugins in a category. */
+export function getPluginsByCategory(category: 'tech' | 'team'): PluginConfig[] {
+  return Object.values(PLUGINS).filter((p) => p.category === category);
+}
+
+/** Get all plugins in a sub-category. */
+export function getPluginsBySubCategory(
+  subCategory: PluginConfig['subCategory']
+): PluginConfig[] {
+  return Object.values(PLUGINS).filter((p) => p.subCategory === subCategory);
+}
+
+/**
+ * Get all skill names from selected plugins.
+ * Returns only non-null skill names for the given tool IDs.
+ */
+export function getSelectedSkillNames(toolIds: string[]): string[] {
+  return toolIds
+    .map((id) => PLUGINS[id]?.skillName)
+    .filter((s): s is string => s !== null);
+}
+
+/**
+ * All possible tool-specific skill names (used to compute exclusions).
+ */
+export const ALL_PLUGIN_SKILL_NAMES: string[] = Object.values(PLUGINS)
+  .map((p) => p.skillName)
+  .filter((s): s is string => s !== null);

package/src/orchestrator/{skills/jira-management → plugins/jira}/SKILL.md

@@ -3,11 +3,11 @@ name: jira-management
 description: "Jira board conventions for tracking feature work — issue naming, labels, priorities, status workflow, and session continuity via Atlassian Rovo MCP. Use when decomposing features into tasks or resuming interrupted sessions."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Task Management with Jira
 
-Conventions for tracking feature work on Jira via the Atlassian Rovo MCP server. For project-specific project keys, workflow state IDs, and board configuration, see [jira-config.md](../../customizations/project/jira-config.md).
+Conventions for tracking feature work on Jira via the Atlassian Rovo MCP server. For project-specific project keys, workflow state IDs, and board configuration, see [tracker-config.md](../../customizations/project/tracker-config.md).
 
 ## Atlassian Rovo MCP Server
 
@@ -167,4 +167,4 @@ project = PROJ AND sprint in openSprints() ORDER BY priority DESC
 project = PROJ AND priority = Highest AND status != Done
 ```
 
-Replace `PROJ` with the actual project key from [jira-config.md](../../customizations/project/jira-config.md).
+Replace `PROJ` with the actual project key from [tracker-config.md](../../customizations/project/tracker-config.md).

package/src/orchestrator/plugins/jira/config.ts

@@ -0,0 +1,30 @@
+import type { PluginConfig } from '../types.js';
+
+export const config: PluginConfig = {
+  id: 'jira',
+  name: 'Jira',
+  category: 'team',
+  subCategory: 'tracker',
+  label: 'Jira',
+  hint: 'Atlassian issue tracking via Rovo MCP',
+  skillName: 'jira-management',
+  mcpServerKey: 'Jira',
+  mcpConfig: {
+    type: 'http',
+    url: 'https://mcp.atlassian.com/v1/mcp',
+  },
+  authType: 'oauth',
+  envVars: [],
+  agentToolMap: {
+    'team-lead': [
+      'Jira/searchJiraIssuesUsingJql', 'Jira/getJiraIssue', 'Jira/createJiraIssue',
+      'Jira/addCommentToJiraIssue', 'Jira/getJiraProjectIssueTypesMetadata',
+      'Jira/getJiraIssueTypeMetaWithFields', 'Jira/search',
+      'Jira/getConfluencePage', 'Jira/searchConfluenceUsingCql',
+      'Jira/getAccessibleAtlassianResources',
+    ],
+  },
+  docsUrl: null,
+  officialDocs: 'https://developer.atlassian.com/cloud/jira/platform/',
+  mcpPackage: null,
+};

package/src/orchestrator/{skills/task-management → plugins/linear}/SKILL.md

@@ -1,13 +1,13 @@
 ---
-name: task-management
+name: linear-task-management
 description: "Linear board conventions for tracking feature work — issue naming, labels, priorities, status workflow, and session continuity. Use when decomposing features into tasks or resuming interrupted sessions."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Task Management with Linear
 
-Conventions for tracking feature work on the Linear board via MCP tools. For project-specific team ID, workflow state UUIDs, and label UUIDs, see [linear-config.md](../../customizations/project/linear-config.md).
+Conventions for tracking feature work on the Linear board via MCP tools. For project-specific team ID, workflow state UUIDs, and label UUIDs, see [tracker-config.md](../../customizations/project/tracker-config.md).
 
 ## Discovered Issues (Bug Tickets)
 

package/src/orchestrator/plugins/linear/config.ts

@@ -0,0 +1,34 @@
+import type { PluginConfig } from '../types.js';
+
+export const config: PluginConfig = {
+  id: 'linear',
+  name: 'Linear',
+  category: 'team',
+  subCategory: 'tracker',
+  label: 'Linear',
+  hint: 'Issue tracking with MCP integration',
+  skillName: 'linear-task-management',
+  mcpServerKey: 'Linear',
+  mcpConfig: {
+    type: 'stdio',
+    command: 'npx',
+    args: ['-y', '@mseep/linear-mcp'],
+    envFile: '${workspaceFolder}/.env',
+  },
+  authType: 'env-token',
+  envVars: [
+    {
+      name: 'LINEAR_API_KEY',
+      hint: 'Create at linear.app → Settings → API → Personal API keys',
+    },
+  ],
+  agentToolMap: {
+    'team-lead': [
+      'linear/create_issue', 'linear/list_issues', 'linear/update_issue',
+      'linear/list_teams', 'linear/list_projects', 'linear/get_issue', 'linear/search_issues',
+    ],
+  },
+  docsUrl: '/guides/linear-setup',
+  officialDocs: 'https://linear.app/docs',
+  mcpPackage: '@mseep/linear-mcp',
+};

package/src/orchestrator/{skills/nx-workspace → plugins/nx}/SKILL.md

@@ -3,7 +3,7 @@ name: nx-workspace
 description: "NX monorepo commands, conventions, code generation, and task running patterns. Use when running builds, tests, linting, code generation, or any development commands."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # NX Workspace
 

package/src/orchestrator/plugins/nx/config.ts

@@ -0,0 +1,29 @@
+import type { PluginConfig } from '../types.js';
+
+export const config: PluginConfig = {
+  id: 'nx',
+  name: 'NX',
+  category: 'tech',
+  subCategory: 'monorepo',
+  label: 'NX',
+  hint: 'Monorepo build system',
+  skillName: 'nx-workspace',
+  mcpServerKey: 'Nx',
+  mcpConfig: {
+    type: 'stdio',
+    command: 'npx',
+    args: ['nx', 'mcp'],
+  },
+  authType: 'none',
+  envVars: [],
+  agentToolMap: {
+    'architect': ['nx-mcp-server/nx_workspace', 'nx-mcp-server/nx_project_details', 'nx-mcp-server/nx_visualize_graph'],
+    'developer': ['nx-mcp-server/nx_project_details', 'nx-mcp-server/nx_workspace', 'nx-mcp-server/nx_generators'],
+    'devops-expert': ['nx-mcp-server/nx_project_details', 'nx-mcp-server/nx_workspace', 'nx-mcp-server/nx_workspace_path'],
+    'performance-expert': ['nx-mcp-server/nx_project_details', 'nx-mcp-server/nx_workspace'],
+    'release-manager': ['nx-mcp-server/nx_project_details', 'nx-mcp-server/nx_workspace', 'nx-mcp-server/nx_workspace_path'],
+  },
+  docsUrl: null,
+  officialDocs: 'https://nx.dev/getting-started/intro',
+  mcpPackage: null,
+};

package/src/orchestrator/{skills/sanity-cms → plugins/sanity}/SKILL.md

@@ -3,7 +3,7 @@ name: sanity-cms
 description: "Sanity CMS development rules, GROQ query patterns, and content management best practices. Use when working with Sanity schemas, writing GROQ queries, modifying content models, or managing CMS configuration."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Sanity CMS
 

package/src/orchestrator/plugins/sanity/config.ts

@@ -0,0 +1,44 @@
+import type { PluginConfig } from '../types.js';
+
+export const config: PluginConfig = {
+  id: 'sanity',
+  name: 'Sanity',
+  category: 'tech',
+  subCategory: 'cms',
+  label: 'Sanity',
+  hint: 'GROQ queries, real-time collaboration',
+  skillName: 'sanity-cms',
+  mcpServerKey: 'Sanity',
+  mcpConfig: {
+    type: 'http',
+    url: 'https://mcp.sanity.io',
+  },
+  authType: 'oauth',
+  envVars: [],
+  agentToolMap: {
+    'content-engineer': [
+      'sanity/get_schema', 'sanity/get_sanity_rules', 'sanity/list_sanity_rules',
+      'sanity/query_documents', 'sanity/get_document', 'sanity/create_documents_from_json',
+      'sanity/create_documents_from_markdown', 'sanity/patch_document_from_json',
+      'sanity/patch_document_from_markdown', 'sanity/deploy_schema', 'sanity/publish_documents',
+      'sanity/unpublish_documents', 'sanity/discard_drafts', 'sanity/list_projects',
+      'sanity/list_datasets', 'sanity/list_workspace_schemas', 'sanity/list_embeddings_indices',
+      'sanity/search_docs', 'sanity/read_docs', 'sanity/semantic_search',
+      'sanity/migration_guide', 'sanity/create_version', 'sanity/generate_image',
+      'sanity/transform_image', 'sanity/add_cors_origin',
+    ],
+    'copywriter': [
+      'sanity/get_schema', 'sanity/query_documents', 'sanity/get_document',
+      'sanity/patch_document_from_json', 'sanity/patch_document_from_markdown',
+      'sanity/list_datasets', 'sanity/list_projects',
+    ],
+    'data-expert': [
+      'sanity/get_schema', 'sanity/query_documents', 'sanity/create_documents_from_json',
+      'sanity/patch_document_from_json', 'sanity/get_document', 'sanity/list_datasets',
+      'sanity/list_projects',
+    ],
+  },
+  docsUrl: null,
+  officialDocs: 'https://www.sanity.io/docs',
+  mcpPackage: null,
+};

package/src/orchestrator/{skills/slack-notifications → plugins/slack}/SKILL.md

@@ -3,7 +3,7 @@ name: slack-notifications
 description: "Slack MCP integration for agent-to-human notifications and bi-directional communication. Use when agents need to post progress updates, request approvals, or read user responses via Slack channels and threads."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Slack Notifications
 
@@ -232,7 +232,7 @@ Project-specific channel mappings are defined in `.github/customizations/stack/n
 
 - **Always thread replies** — never post top-level messages for follow-ups
 - **One thread per task** — keep all updates for a single task in one thread
-- **Include task ID** — every message references the Linear/Jira issue ID
+- **Include task ID** — every message references the tracker issue ID
 - **Pin important threads** — pin approval requests and blocking issues
 
 ## Message Formatting

package/src/orchestrator/plugins/slack/config.ts

@@ -0,0 +1,35 @@
+import type { PluginConfig } from '../types.js';
+
+export const config: PluginConfig = {
+  id: 'slack',
+  name: 'Slack',
+  category: 'team',
+  subCategory: 'notifications',
+  label: 'Slack',
+  hint: 'Agent notifications and communication',
+  skillName: 'slack-notifications',
+  mcpServerKey: 'Slack',
+  mcpConfig: {
+    type: 'stdio',
+    command: 'npx',
+    args: ['-y', '@kazuph/mcp-slack'],
+    envFile: '${workspaceFolder}/.env',
+    env: {
+      SLACK_MCP_ADD_MESSAGE_TOOL: 'true',
+    },
+  },
+  authType: 'env-token',
+  envVars: [
+    {
+      name: 'SLACK_MCP_XOXB_TOKEN',
+      hint: 'Create a Slack App at api.slack.com/apps → Bot User OAuth Token',
+    },
+  ],
+  agentToolMap: {
+    'team-lead': ['slack/*'],
+    'release-manager': ['slack/*'],
+  },
+  docsUrl: '/guides/plugins#slack',
+  officialDocs: 'https://api.slack.com/docs',
+  mcpPackage: '@kazuph/mcp-slack',
+};

package/src/orchestrator/{skills/strapi-cms → plugins/strapi}/SKILL.md

@@ -3,7 +3,7 @@ name: strapi-cms
 description: "Strapi CMS development patterns, REST/GraphQL API usage, content type building, plugin development, and deployment best practices. Use when working with Strapi content types, controllers, services, or plugins."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Strapi CMS
 

package/src/orchestrator/plugins/strapi/config.ts

@@ -0,0 +1,41 @@
+import type { PluginConfig } from '../types.js';
+
+export const config: PluginConfig = {
+  id: 'strapi',
+  name: 'Strapi',
+  category: 'tech',
+  subCategory: 'cms',
+  label: 'Strapi',
+  hint: 'Open-source headless CMS',
+  skillName: 'strapi-cms',
+  mcpServerKey: 'Strapi',
+  mcpConfig: {
+    type: 'stdio',
+    command: 'npx',
+    args: ['-y', 'strapi-mcp'],
+  },
+  authType: 'none',
+  envVars: [],
+  agentToolMap: {
+    'content-engineer': [
+      'strapi/list_content_types', 'strapi/get_content_type_schema', 'strapi/get_entries',
+      'strapi/get_entry', 'strapi/create_entry', 'strapi/update_entry', 'strapi/delete_entry',
+      'strapi/publish_entry', 'strapi/unpublish_entry', 'strapi/upload_media',
+      'strapi/upload_media_from_path', 'strapi/connect_relation', 'strapi/disconnect_relation',
+      'strapi/create_content_type', 'strapi/update_content_type', 'strapi/delete_content_type',
+      'strapi/list_components', 'strapi/get_component_schema', 'strapi/create_component',
+      'strapi/update_component',
+    ],
+    'copywriter': [
+      'strapi/list_content_types', 'strapi/get_content_type_schema', 'strapi/get_entries',
+      'strapi/get_entry', 'strapi/update_entry', 'strapi/publish_entry',
+    ],
+    'data-expert': [
+      'strapi/list_content_types', 'strapi/get_content_type_schema', 'strapi/get_entries',
+      'strapi/get_entry', 'strapi/create_entry', 'strapi/update_entry',
+    ],
+  },
+  docsUrl: null,
+  officialDocs: 'https://docs.strapi.io/',
+  mcpPackage: 'strapi-mcp',
+};

package/src/orchestrator/{skills/supabase-database → plugins/supabase}/SKILL.md

@@ -3,7 +3,7 @@ name: supabase-database
 description: "Supabase database migration rules, RLS policy patterns, and auth integration best practices. Use when designing database tables, writing migrations, configuring RLS policies, implementing auth, or managing user roles."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Supabase Database
 

package/src/orchestrator/plugins/supabase/config.ts

@@ -0,0 +1,34 @@
+import type { PluginConfig } from '../types.js';
+
+export const config: PluginConfig = {
+  id: 'supabase',
+  name: 'Supabase',
+  category: 'tech',
+  subCategory: 'database',
+  label: 'Supabase',
+  hint: 'Postgres + Auth + RLS + Edge Functions',
+  skillName: 'supabase-database',
+  mcpServerKey: 'Supabase',
+  mcpConfig: {
+    type: 'http',
+    url: 'https://mcp.supabase.com/mcp',
+  },
+  authType: 'oauth',
+  envVars: [],
+  agentToolMap: {
+    'database-engineer': [
+      'supabase/apply_migration', 'supabase/execute_sql', 'supabase/list_tables',
+      'supabase/list_migrations', 'supabase/list_extensions', 'supabase/get_logs',
+      'supabase/get_project', 'supabase/get_project_url', 'supabase/list_projects',
+      'supabase/search_docs', 'supabase/generate_typescript_types', 'supabase/get_advisors',
+      'supabase/create_branch', 'supabase/list_branches',
+    ],
+    'security-expert': [
+      'supabase/execute_sql', 'supabase/list_tables', 'supabase/get_advisors',
+      'supabase/list_migrations', 'supabase/get_project',
+    ],
+  },
+  docsUrl: null,
+  officialDocs: 'https://supabase.com/docs',
+  mcpPackage: null,
+};

package/src/orchestrator/{skills/teams-notifications → plugins/teams}/SKILL.md

@@ -3,7 +3,7 @@ name: teams-notifications
 description: "Microsoft Teams MCP integration for agent-to-human notifications and bi-directional communication. Use when agents need to post progress updates, request approvals, or read user responses via Teams channels and chats."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Teams Notifications
 
@@ -127,7 +127,7 @@ To check for approvals or instructions:
 
 - **Always reply in threads** — use message replies, not top-level posts for follow-ups
 - **One thread per task** — keep all updates for a single task in one conversation thread
-- **Include task ID** — every message references the Linear/Jira issue ID
+- **Include task ID** — every message references the tracker issue ID
 - **Mark important messages** — use importance flags for approval requests
 
 ### Chat vs Channel

package/src/orchestrator/plugins/teams/config.ts

@@ -0,0 +1,44 @@
+import type { PluginConfig } from '../types.js';
+
+export const config: PluginConfig = {
+  id: 'teams',
+  name: 'Microsoft Teams',
+  category: 'team',
+  subCategory: 'notifications',
+  label: 'Microsoft Teams',
+  hint: 'Agent notifications via Teams channels',
+  skillName: 'teams-notifications',
+  mcpServerKey: 'Teams',
+  mcpConfig: {
+    type: 'http',
+    url: 'https://agent365.svc.cloud.microsoft/agents/tenants/${input:tenant_id}/servers/mcp_TeamsServer',
+  },
+  authType: 'oauth',
+  envVars: [],
+  agentToolMap: {
+    'team-lead': [
+      'Teams/mcp_graph_chat_createChat', 'Teams/mcp_graph_chat_listChats',
+      'Teams/mcp_graph_chat_getChat', 'Teams/mcp_graph_chat_postMessage',
+      'Teams/mcp_graph_chat_listChatMessages', 'Teams/mcp_graph_chat_getChatMessage',
+      'Teams/mcp_graph_teams_listTeams', 'Teams/mcp_graph_teams_listChannels',
+      'Teams/mcp_graph_teams_getChannel', 'Teams/mcp_graph_teams_postChannelMessage',
+      'Teams/mcp_graph_teams_replyToChannelMessage', 'Teams/mcp_graph_teams_listChannelMessages',
+    ],
+    'release-manager': [
+      'Teams/mcp_graph_chat_postMessage', 'Teams/mcp_graph_chat_listChats',
+      'Teams/mcp_graph_teams_listTeams', 'Teams/mcp_graph_teams_listChannels',
+      'Teams/mcp_graph_teams_postChannelMessage', 'Teams/mcp_graph_teams_replyToChannelMessage',
+      'Teams/mcp_graph_teams_listChannelMessages',
+    ],
+  },
+  docsUrl: null,
+  officialDocs: 'https://learn.microsoft.com/en-us/microsoftteams/',
+  mcpPackage: null,
+  mcpInputs: [
+    {
+      id: 'tenant_id',
+      type: 'promptString',
+      description: 'Microsoft Entra tenant ID (GUID)',
+    },
+  ],
+};

package/src/orchestrator/plugins/types.ts

@@ -0,0 +1,79 @@
+/**
+ * Configuration for a tool plugin.
+ * Single source of truth for tool metadata used by init, adapters, and agents.
+ */
+export interface PluginConfig {
+  /** Unique ID matching TechTool | TeamTool union type */
+  id: string;
+
+  /** Human-readable display name */
+  name: string;
+
+  /** Plugin category */
+  category: 'tech' | 'team';
+
+  /** Sub-category for grouping */
+  subCategory: 'cms' | 'database' | 'deployment' | 'monorepo' | 'tracker' | 'notifications' | 'testing';
+
+  /** Label shown in the `npx opencastle init` multiselect */
+  label: string;
+
+  /** Hint shown next to the label in multiselect */
+  hint: string;
+
+  /** Skill directory name (matches the old skills/ dirname). null if no skill. */
+  skillName: string | null;
+
+  /** MCP server key used in the generated MCP config. null if no MCP server. */
+  mcpServerKey: string | null;
+
+  /** Raw MCP server config */
+  mcpConfig: McpServerConfig;
+
+  /** Authentication type */
+  authType: 'oauth' | 'env-token' | 'none';
+
+  /** Required environment variables for this plugin */
+  envVars: EnvVarRequirement[];
+
+  /** Tools to inject into specific agent definitions when this plugin is selected.
+   * Key = agent name (e.g. 'content-engineer'), Value = tool names to append. */
+  agentToolMap?: Record<string, string[]>;
+
+  /** URL to setup guide on opencastle.dev (null if none) */
+  docsUrl: string | null;
+
+  /** Official product documentation URL */
+  officialDocs: string;
+
+  /** NPM package for the MCP server (null for HTTP/OAuth servers) */
+  mcpPackage: string | null;
+
+  /** Whether this plugin should be preselected in the init prompt */
+  preselected?: boolean;
+
+  /** VS Code input prompts required by this plugin's MCP config (e.g. tenant ID) */
+  mcpInputs?: McpInput[];
+}
+
+export interface McpInput {
+  id: string;
+  type: 'promptString';
+  description: string;
+}
+
+export interface McpServerConfig {
+  type: 'stdio' | 'http';
+  command?: string;
+  args?: string[];
+  url?: string;
+  env?: Record<string, string>;
+  envFile?: string;
+}
+
+export interface EnvVarRequirement {
+  /** Environment variable name */
+  name: string;
+  /** Short description of where to get the value */
+  hint: string;
+}

package/src/orchestrator/plugins/vercel/config.ts

@@ -0,0 +1,33 @@
+import type { PluginConfig } from '../types.js';
+
+export const config: PluginConfig = {
+  id: 'vercel',
+  name: 'Vercel',
+  category: 'tech',
+  subCategory: 'deployment',
+  label: 'Vercel',
+  hint: 'Deployment and hosting platform',
+  skillName: null,
+  mcpServerKey: 'Vercel',
+  mcpConfig: {
+    type: 'http',
+    url: 'https://mcp.vercel.com',
+  },
+  authType: 'oauth',
+  envVars: [],
+  agentToolMap: {
+    'devops-expert': [
+      'vercel/deploy_to_vercel', 'vercel/get_deployment', 'vercel/get_deployment_build_logs',
+      'vercel/get_project', 'vercel/get_runtime_logs', 'vercel/list_deployments',
+      'vercel/list_projects', 'vercel/list_teams', 'vercel/search_vercel_documentation',
+      'vercel/check_domain_availability_and_price',
+    ],
+    'release-manager': [
+      'vercel/get_deployment', 'vercel/get_deployment_build_logs',
+      'vercel/get_runtime_logs', 'vercel/list_deployments', 'vercel/list_projects',
+    ],
+  },
+  docsUrl: null,
+  officialDocs: 'https://vercel.com/docs',
+  mcpPackage: null,
+};