Create Plugin

To scaffold a Copilot CLI plugin, you need a structured workflow that guides you through planning, implementation, and validation. A phase-driven process eliminates boilerplate by automating discovery, scaffolding components like skills and hooks, and generating validated artifacts.

The best way to structure Copilot CLI plugin development is using a phase-driven lifecycle from concept to release. This involves structured component planning for skills, agents, hooks, MCPs, and settings, ensuring all elements are properly organized before implementation and validation.

Yes, you need a SKILL.md file to create a Copilot CLI plugin. The file must include frontmatter with a name and description to initiate the workflow. You can also use optional resource directories to organize scripts, references, and assets for the plugin.

Plugin validation in a Copilot CLI workflow works through built-in validation checkpoints and references to evaluation utilities. This ensures the scaffolded components function correctly and meet requirements before the plugin is considered a validated artifact ready for release.

Yes, you can use multi-phase workflows for Copilot CLI plugin creation. The process supports multi-phase workflows that automate the end-to-end creation cycle, covering discovery, planning, implementation, validation, and documentation to guide developers from initial concept to final release.

When developing a Copilot CLI plugin, you should plan components including skills, agents, hooks, MCPs, and settings. Structured component planning during the scaffolding phase ensures each part of the plugin lifecycle is properly configured before implementation and validation.