create-cowork-plugin

To build a Cowork plugin, you need a guided development process covering discovery, component planning, design, implementation, and packaging to generate the final .plugin file. The workflow ensures correct manifest files and component schemas are created.

When developing a Cowork extension, you can configure commands, skills, agents, hooks, and MCP server configurations. The plugin architecture supports these components alongside the required manifest files and directory structure.

Generating a packaged .plugin file requires access to an outputs directory for delivering the final build. This directory is where the packaged plugin is placed after the implementation and packaging stages are complete.

The best way to structure a plugin manifest for Cowork is to follow encoded best practices for directory structure and component schemas. The guided process helps you define the manifest files alongside commands, skills, and MCP servers.

You can integrate an internal ticketing system by using this plugin development process to define the necessary commands, skills, and MCP servers. It guides you from concept through packaging to produce a functional .plugin file for the integration.