A workflow is the way you work, written down once so an agent follows it every time. Not a prompt you retype, and not a suggestion: NIBWP injects the workflow into the agent as mandatory context, so the same job is done the same way on site one and site one hundred.
Workflows are structured playbooks stored on your own site: when to use them, the principles to hold, the ordered steps, the hard constraints, the checks, and the report to hand back. Pin one to make it always-on, or let NIBWP load it automatically when a task matches its when-to-use. Part of Pro and the Bundle.
What a workflow holds
Each workflow is a saved playbook with the parts an agent needs in order to act like someone who has done the job before:
| Part | What it decides |
|---|---|
| When to use | The trigger. NIBWP reads this to auto-route a matching task to the workflow. |
| Principles | The standards to hold while working — the things you would otherwise repeat. |
| Steps | The ordered process, so nothing is skipped and the order is not improvised. |
| Constraints | The hard limits: what must never happen, whatever the agent thinks. |
| Validation | The checks to run before calling the work done. |
| Report | What to hand back, so the result is readable by a person or a client. |
| Tools | The plugins, themes and skills the workflow relies on, with live detection status. |
Pinned, or routed automatically
A pinned workflow is always-on: its playbook is injected as strict context on every request, which is how you enforce a house rule such as planning and asking before anything is applied. A workflow that is not pinned still gets used — the agent loads it by itself when the task matches its when-to-use.
Starters you already have
NIBWP ships a set of ready-made workflows across building sites, SEO audits, content passes, converting a design, and making safe changes. They seed themselves, so the Workflows screen is useful before you write anything. Duplicate one, change what you need, and it becomes yours — the original stays intact.
Private, licence circle, or community
Every workflow has a visibility:
- Private — it stays on this site. This is the default.
- License Circle — every site on your licence can use it, which is how an agency runs one method everywhere.
- Community — offered to other NIBWP users through the Library, where workflows can be browsed, upvoted and imported.
Importing gives you your own editable copy, so a community workflow never changes under you.
The abilities behind it
| Ability | What it does |
|---|---|
nibwp/list-workflows | List saved workflows with their summary, when-to-use, pinned state and tool status |
nibwp/get-workflow | Read one workflow in full |
nibwp/save-workflow | Write a new workflow |
nibwp/update-workflow | Change an existing one |
nibwp/activate-workflow | Pin or unpin a workflow |
You rarely call these yourself. Ask the assistant to write the workflow down and it does, and the playbook is saved on your site as a normal post type with revisions, so you can roll back a change.
Why it matters
- The method survives the session — the way you work is not re-explained each time.
- The same job, the same way — one method across every site on your licence.
- Fewer surprises — constraints and validation are part of the instructions, not an afterthought.
- Yours to change — plain text on your own site, with revisions behind it.
FAQ
Do I need Pro?
Where are workflows stored?
What is the difference between a workflow and a skill?
Can I share one with my other sites?
Write the way you work, once
Turn the method you repeat into a playbook every agent follows.
Get NIBWP Pro