Workflows

Put the agent on rails.

A Workflow is a procedure your AI must follow — principles, process, strict rules, validation, and a structured report — injected into every request. Not a suggestion the model can ignore: mandatory operating instructions that keep an agent governed and on-system, on your live client sites, every single run.

18
default playbooks
9
categories
1
always-on at a time
The gap

Your AI is brilliant. And inconsistent.

The same prompt builds a great site on Monday and a different one on Tuesday. That gap is exactly what you cannot bill for.

!
It improvises

Ask twice, get two answers. No two client sites come out the same way.

!
You babysit it

Pasting the same instructions into chat before every task, on every site, forever.

!
It does not scale

The process lives in your head, so the quality leaves the room when you do.

// the fix

Put the process on rails.

Write your method down once as a Workflow. NibWP feeds it to the agent as mandatory rules, so every run lands the same — predictable enough to bill, repeatable enough to sell. Here is how:

  • Write your method once as a Markdown playbook.
  • Add the principles, ordered steps, hard rules and validation.
  • Pin it for every task, or let it auto-route by trigger.
  • Every run follows it and ends with a client-ready report.

The same senior procedure on every site — by design, not by hope.

Letting an agent loose on a client's live WordPress is the thing teams are right to fear. Workflows remove the gamble: the agent works inside a procedure you set, validates its own output against your rules, and reports back. Pair that with NibWP's typed tools, scoped permissions and audit log and you get AI speed with senior-developer discipline — repeatable on site one and site one hundred.

What a Workflow is

Not code. A procedure your AI obeys.

A Workflow is a structured playbook NibWP injects as mandatory instructions — the opinionated recipe that conducts your tools and expertise toward one outcome.

Layer 1
Abilities
The 132 typed MCP tools your agent can call.
Layer 2
Skills
Validated, builder-aware expertise packs for every builder.
Layer 3
Workflows
The procedure that conducts them toward results.
// every playbook runs the same six-step spineends with a client-ready report
01
When to use
The trigger that loads it
02
Principles
The standards it upholds
03
Process
The ordered steps
04
Rules
The hard constraints
05
Validation
The checks before done
06
Report
What you hand the client
What it does

Workflows: define it once, run it forever.

Some jobs are the same every time — a launch checklist, a fresh site setup, a monthly content refresh. Capture one as a Workflow and you never wire it up by hand again: describe the steps once, then run the whole thing on command and get back the same finished result, every single time.

01

Build it once

Capture a multi-step job as a single Workflow — the pages to create, the fields to fill, the automations to wire up. Set the steps in plain language, no scripting.

02

Run it on command

Trigger the whole thing whenever you need it. The agent runs every step in order and hands back the finished result, ready to use — no babysitting.

03

Identical every run

No drift, no 'it worked last time.' You get the exact same outcome on run one and run one hundred — reliable enough to hand to your whole team.

How they run

Three ways a Workflow reaches your agent.

Your AI client connects over MCP, asks NibWP what it can do, and is handed the Workflows automatically. No copy-paste needed.

Pinned

Always on

The pinned Workflow is injected into every request as a strict block the agent must always follow. Pinning one unpins the rest — exactly one always-on rule governs the site at a time.

Auto-route

Fires when relevant

Every Workflow — pinned or not — is listed with its 'when to use'. When your task matches, the agent loads and follows that playbook on its own. An unpinned Workflow still fires when it's the right one for the job.

Copy Prompt

On demand

Prefer to trigger one yourself? Each Workflow has a ready-made prompt you copy and paste into your AI to run it on the spot.

// pinned + auto-route coexist — your pinned playbook is always honoured

Why agencies run on Workflows

Standardise the work. Keep the margin.

01

On-rails, every time

Process, rules and validation stop the agent improvising. Every run ends with a structured report, predictable enough to bill.

02

No copy-paste, no babysitting

Your AI reads the workflows live over MCP and follows them. No instructions pasted into chat before every task, on any site you connect.

03

One process, every client site

Standardise how the whole team builds, audits and migrates. New hire or veteran, the result is the same across your portfolio.

04

It improves itself

The agent can capture a successful run as a new playbook, then reuse it. Your library gets sharper the more you work.

Ready to run

18 default playbooks, across 9 categories.

Seeded and ready the moment you connect — pin one, let the agent auto-route, or copy its prompt. Build your own too; the agent can even author its own.

Build your own. Unlimited.

The 18 are just the start. Write as many custom Workflows as you want and run them as often as you like — no cap on how many you create, no cap on how often they run.

Build sites4
  • Build from screenshot
  • Build from HTML
  • Full site build
  • Standard page build
Forms & automations2
  • Contact form
  • Automation setup
SEO3
  • Full SEO audit
  • SEO content pass
  • Fix 404s & redirects
Content2
  • Content creation
  • Content cleanup
Maintenance4
  • Safe changes
  • Site audit report
  • Pre-launch checklist
  • Performance tune
E-commerce2
  • WooCommerce product
  • CPT & fields
Distribute & license

Your workflows are assets. Distribute them on your terms.

A playbook is portable expertise. Keep it private to one site, share it across every site on your license, or give it to the community for free — you choose.

One playbook can travel anywhere a NibWP install runs.

Built once, a Workflow is a portable file. It follows your license to every site you own, or goes out to the whole community — without giving up control of your account.

Private

this site only

The playbook stays on the single site it was created on. Nobody else can see it or run it.

  • Lives on one install, full stop
  • Your private in-house method
  • Never leaves this site

License

every site on your license

Share it across all the websites where your NibWP license is activated. Build it once, run it on every site you own.

  • Auto-shared with your licensed sites
  • One method across your whole portfolio
  • Update once and every site follows

Community

give it away free

Publish it free to the NibWP Library so anyone can import and run it. Build your reputation in the community.

  • Free for everyone to import
  • Climb the community upvotes
  • One-click import, deduped on the way in
You stay in control. Imports are deduped against what you already run, so a shared playbook drops in cleanly — no duplicates, no overwrites, no surprises.
Built in. Built to grow.

A library that gets better with use.

Your agent writes its own

Five MCP abilities let the AI list, get, save, update and activate workflows, authoring and refining playbooks in the same store you manage.

Pull from the library

Browse curated and community playbooks in the NibWP Library and import them in one click, deduped against what you already have.

Upvote the best

Workflows carry a cross-install vote count, so the most useful playbooks rise to the top. Pure social proof, one vote per install.

Pro & Bundle

Give your agent a procedure, not free rein.

Install NibWP, pin a Workflow, and let any AI client run governed, repeatable work across every site you manage — safely, on live, with a report at the end.