Part of the AI Building Blocks for WordPress initiative
- Purpose: provide a common way for WordPress core, plugins, and themes to describe what they can do ("abilities") in a machine‑readable, human‑friendly form.
- Scope: discovery, permissioning, and execution metadata only. Actual business logic stays inside the registering component.
- Audience: plugin & theme authors, agency builders, and future AI / automation tools.
- Discoverability - every ability can be listed, queried, and inspected.
- Interoperability - a uniform schema lets unrelated components compose workflows.
- Security‑first - explicit permissions determine who/what may invoke an ability.
- Gradual adoption - ships first as a Composer package, migrates smoothly to core.
- Introduction
- Getting Started
- Registering Abilities
- Using Abilities
- REST API Reference
- Hooks
- Contributing Guidelines
- wp‑feature‑api - shared vision of declaring capabilities at the PHP layer.
- Command Palette experiments in Gutenberg.
- Modern AI assistant protocols (MCP, A2A).
| Milestone | State |
|---|---|
| Placeholder repository | created |
| Spec draft | created |
| Prototype plugin & Composer package | created |
| Community feedback (#core‑ai Slack) | in progress |
| Core proposal | planned |
- Discuss:
#core-aichannel on WordPress Slack. - File issues: suggestions & use‑cases welcome in this repo.
- Prototype: experiment with the feature plugin or the
wordpress/abilities-apiComposer package.
WordPress is free software, and is released under the terms of the GNU General Public License version 2 or (at your option) any later version. See LICENSE.md for complete license.
