How it works

Inside the AI pipeline

When you press Approve & Build, BuildPlugins.ai runs a chain of 12 specialised AI agents. Each one has a narrow job — and each one's output feeds into the next. Here's what they do.

Typical build time: 2–5 minutes. Complex WooCommerce plugins can take up to 8 minutes.

1

Idea Interpreter

Fast

Reads your raw idea and converts it into a structured intent object: core goal, plugin type, named integrations, constraints, and clarifying questions.

Plugin type (standalone, WooCommerce extension, admin tool…)Primary goal + secondary goalsNamed third-party integrations0–5 clarifying questions
2

Requirements Agent

Fast

Takes your idea plus any clarifying answers and expands them into a concrete feature list. Each feature gets a complexity rating, a database flag, and an API flag.

Feature list with IDs and acceptance criteriaNon-features (explicit scope exclusions)Third-party dependenciesOverall complexity signal
3

UX Agent

Fast

Designs the user-facing side of the plugin: which admin menus and settings pages it needs, what frontend components it renders, and how notifications work.

Settings fields (text, select, checkbox…)Admin pages and parent menusFrontend components (widget, shortcode, block…)Notification types
4

Scope Agent

Fast

Turns the feature list into a final plugin name, slug, and credit estimate. Decides which features are in-scope vs excluded and flags anything the user should know about before building.

Plugin name and slugCredit cost estimateScope warnings (complexity, risk, WC cautions)
5

Risk Agent

Fast

Scans the spec for anything that could cause WordPress.org reviewers to reject the submission or raise security concerns. Flags are shown on the scope review screen before you approve.

Risk flags (external HTTP calls, stored data, capability checks…)WooCommerce-specific cautions
6

Architect Agent

Powerful (with thinking)

Designs the full PHP class structure, hook map, database schema (if needed), and REST endpoints. This is the longest-running agent and uses extended thinking for complex plugins.

Module list with hooks and callbacksDatabase tables and columnsREST API routesPHP class hierarchy
7

Conflict Detection Agent

Fast

Checks the architect's plan for internal contradictions: duplicate hooks, option-key collisions, feature overlaps, and WooCommerce hook hazards.

Conflict list (blocks build on critical conflicts)Warnings (proceed with caution)
8

WordPress Specialist

Powerful (streaming)

Generates all the PHP files: bootstrap, includes, admin pages, REST handlers, templates, and assets. Follows WordPress coding standards and uses the architecture from stage 6.

All plugin PHP filesCSS / JS assetsUninstall script
9

WooCommerce Specialist

Powerful (streaming, conditional)

Only runs if your plugin touches WooCommerce. Adds WC-specific hooks, templates, and compatibility checks on top of the WordPress Specialist output.

WC hook implementationsCart/checkout modificationsOrder management code
10

Security Agent

Fast

Reviews the generated PHP for the most common WordPress security issues: nonce verification, capability checks, SQL injection via $wpdb, and unsafe data handling.

Security issue listFixed code (applied before QA)
11

QA Agent

Fast

Checks the plugin code for correctness: missing function definitions, undefined constants, compatibility issues, and logic errors. If the QA score is low, a repair agent runs to fix specific issues.

QA score (0–100)Issue listRepaired files (if score < 70)
12

Packaging Agent

Fast

Assembles all files into a correctly-structured WordPress plugin ZIP. Adds a readme.txt, normalises file paths, injects the in-plugin feedback widget, and runs a final validation pass.

Plugin ZIP (ready to upload to WordPress)readme.txtpackage_manifest.json

Readme optimisation

After packaging, a separate readme agent generates a WordPress.org-compliant readme.txt — correct headings, FAQ section, privacy disclosure, short description under 150 characters, and 3–5 accurate tags. The validator blocks marketing fluff phrases that WordPress.org rejects.

You can review, edit, and AI-revise the readme from the Project Details page before submitting to WordPress.org.

Model tiers

Not every agent needs the most powerful model. BuildPlugins.ai routes each stage to the appropriate tier to balance speed, quality, and cost:

TierUsed for
FastIdea analysis, requirements, UX, scope, risk, conflict detection, security, QA, packaging
PowerfulArchitecture (with extended thinking on complex builds), WordPress Specialist, WooCommerce Specialist (streaming)