As of 13 August 2026, AI can only partly create a WordPress plugin for your business.

What to actually do

1. Hand it to a person

   The route this page recommends

   Someone with a licence or accountable authority has to sign this before it counts.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, developer skill, and roughly 2 hours until you can act on the result.

   How to actually do it

   1. Open a staging copy of your WordPress site and record its WordPress version, PHP version, active plugins, user roles and the business action the plugin must perform.
   2. Write the required behaviour, stored data, users who may access it, external services, admin settings and failure behaviour in a plain requirements document.
   3. Paste that document into the prompt, answer the model's clarification questions, and require it to produce the file tree and complete files without inventing credentials or API details.
   4. Create the plugin folder and files in a local development environment, paste in the generated code, and ask the model to resolve syntax errors or missing dependencies shown by your development tools.
   5. Install the plugin only on staging, then run the generated tests for authorised and unauthorised users, invalid input, failed requests, duplicate actions, upgrades and uninstall.
   6. Compare every API call, WordPress hook, permission, database query and data-handling decision against the current WordPress and service documentation, and have a WordPress developer inspect the code for security issues.
   7. Back up the live site, deploy the reviewed plugin during a controlled change window, and check logs and the affected business process before enabling it for all users.

   Prompt

   Create a production-ready WordPress plugin for the following business requirement:
   
   Business requirement:
   [DESCRIBE WHAT THE PLUGIN MUST DO]
   
   WordPress version: [VERSION OR UNKNOWN]
   PHP version: [VERSION OR UNKNOWN]
   Other plugins or services it must work with: [LIST OR NONE]
   User roles allowed to use it: [ROLES]
   Data it reads, stores or sends: [DATA]
   External APIs and authentication method: [DETAILS OR NONE]
   Admin settings required: [DETAILS]
   Frontend behaviour required: [DETAILS]
   
   First, identify missing or ambiguous requirements and ask only the questions that could change the implementation. Do not invent API endpoints, credentials, business rules, permissions or compliance claims. Then provide:
   1. A short implementation plan and file tree.
   2. Complete plugin code in separate clearly labelled files, using a unique prefixed function and class namespace to avoid collisions.
   3. Secure WordPress practices, including capability checks, nonces, sanitisation, validation, escaping, prepared database queries and safe handling of secrets where relevant.
   4. Activation, deactivation and uninstall behaviour, including what happens to stored data.
   5. Installation instructions for a staging site, without asking me to paste secrets into the chat.
   6. A test plan covering normal use, invalid input, unauthorised users, failed API calls, duplicate actions, upgrades and uninstall.
   7. A list of claims that require checking against the current WordPress and third-party documentation.
   
   Do not say the plugin is tested, secure or production-ready unless the evidence supplied here proves it. If a requirement needs a paid service, server access or a human security review, state that plainly. Finish by giving the complete code and a concise list of what I must verify before deployment.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.