Work IQ Dev Tools: build Copilot extensions
Microsoft Copilot

Work IQ Dev Tools: build Copilot extensions

by HubSite 365 about Microsoft

Software Development Redmond, Washington

Work IQ Dev Tools gives developers a CLI and AI-assisted workflow to build, validate, and package Microsoft 365 Copilot extensions.

Key insights

  • Work IQ Dev Tools is in developer preview.
  • WIQD supports natural-language, AI-assisted development and a command-line workflow.
  • A plugin can combine reusable skills, remote MCP connectors, and a declarative agent.
  • The demo locally validates the generated extension before it is enabled in Copilot Cowork.
  • The demonstrated extension is configured for Copilot Chat and Cowork.

Work IQ Dev Tools (WIQD) gives developers an AI-assisted workflow and command-line interface for building Microsoft 365 Copilot extensions, from an initial idea through local validation and packaging. It is aimed at developers creating skills, connectors, plugins, or declarative agents for Copilot experiences. Microsoft demonstrates the workflow by building a Zava employee claims extension and trying it in Copilot Cowork.

What's new

WIQD brings several Copilot extension development tasks into one developer experience. In the demonstration, a developer describes the desired outcome in natural language, then the tools help generate the extension’s components and validate them locally. The command-line interface provides another way to carry out the workflow, including for more repeatable development steps.

The important packaging idea is that an extension can combine multiple capabilities. A plugin can include skills, a remote MCP connector, and a declarative agent rather than treating the conversational agent as the whole product. Skills provide reusable instructions or workflows; an MCP connector exposes tools and data through a remote server; and a declarative agent provides a conversational experience.

These parts can also be used independently or combined in different ways. In the Zava example, WIQD creates a declarative agent, an MCP connector for claims actions, and shared skills for tasks such as claim risk assessment and employee onboarding. The presenter describes the plugin model as a way to group those capabilities in a Microsoft 365 app package.

Who it is for and what you need

WIQD is for developers building or extending Microsoft 365 Copilot experiences. The demonstration is developer-focused: it uses a coding environment, a natural-language requirement, a website containing onboarding information, and an available MCP server. Developers can choose an AI-assisted workflow or use the CLI.

Microsoft describes the tools as being in developer preview. The demonstrated workflow uses an initial EULA acceptance on the machine before it proceeds. It also relies on having an MCP server available when the extension needs external tools or data. For the sample agent, the developer supplies the relevant website so the generated agent can use it as a source for onboarding information.

WIQD is presented as part of the broader Copilot developer experience, and the demonstration refers to native integration with Agent Toolkit concepts. For background on adjacent tooling, see our coverage of developer tools.

How it works

The sample starts with a business requirement rather than a list of implementation details. The developer asks for an extension that helps employees manage claims, supports changes through the user experience, works in Copilot Chat and Cowork, and helps with onboarding. WIQD interprets the request and builds the parts needed for that scenario.

  1. Describe the extension’s purpose and the user outcome in a coding harness that supports the relevant plugins and skills.
  2. Provide the MCP server and relevant knowledge, such as the onboarding site, for the extension to use.
  3. Let the AI-assisted workflow scaffold the package, including its manifest, skills, connector, and declarative agent. Alternatively, use WIQD’s CLI for command-line operations.
  4. Review and locally validate the generated agent and package. In the demo, local validation uses libraries that the presenter says were previously available during deployment.
  5. Enable the local extension in Copilot Cowork and try a task, such as requesting an open claims dashboard. The presenter says the same demonstrated experience works in Copilot Chat.

The generated skills in the example are markdown instructions. The manifest includes an agent connector that represents the remote MCP server, while the declarative agent contains behavior and references to the provided sites. The presenter also describes authentication options for the connector, including OAuth, Entra single sign-on, and dynamic client registration.

Limitations and alternatives

WIQD is in developer preview, so teams should treat it as preview tooling when deciding how to incorporate it into established development processes. The workflow does not remove the need for developers to review the output: the demo shows generated configuration and local validation, but those steps are not a substitute for checking whether the extension meets a team’s requirements.

The AI-assisted path depends on a coding harness that supports the tools. The presenter names GitHub Copilot, Claude Code, Codex, OpenCode, Antigravity, and Gemini as examples, and also discusses using the tools in VS Code and the Copilot app. The CLI is an alternative when a team wants a more deterministic workflow or wants to incorporate commands into CI/CD processes.

Teams should also examine the capabilities and access needs of the MCP server they connect, and review the generated package before sharing it. The example’s local testing is in Cowork, with Copilot Chat also named as a supported surface for that extension. Broader publishing is described as a workflow that can lead to Partner Center and the public marketplace.

Sources

Frequently asked questions

Is Work IQ Dev Tools generally available?

Work IQ Dev Tools is in developer preview.

What can a Work IQ Dev Tools plugin contain?

A plugin can combine reusable skills, remote MCP connectors, and a declarative agent. The capabilities can also be used in different combinations.

Can developers use Work IQ Dev Tools from the command line?

Yes. WIQD includes a CLI as an alternative to its AI-assisted workflow, including for more deterministic processes and CI/CD use.

How do you test a Copilot extension built with WIQD?

The demonstrated workflow locally validates the generated agent and package, then enables the extension in Copilot Cowork for a task-based test. The presenter says the sample also works in Copilot Chat.