Build a knowledge base

Standing up a help center is a lot of small, boring steps: decide the categories, create each one, draft an article for every common question, then build a menu so people can find it. It is the kind of job that stalls at the planning stage because the setup is tedious and you would rather write the answers than click through the term editor.

This hands the scaffolding to the agent. It plans the whole thing on paper first, you approve the shape, and only then does it build.

I want to build a help center on this site. Work in two phases and do not
create anything in the first phase.

Phase one, planning only: read my existing posts and categories so we do not
duplicate what is already here, then propose a structure. I want a short list
of help categories (something like Getting started, Billing, Troubleshooting),
the article titles that belong under each, and a nav menu that links to each
category. Hand me the whole plan as an outline and stop.

I will edit the outline and tell you to go. Only then, phase two: create the
approved categories first, then draft each article into the right category as
an unpublished draft, working in small batches and showing me each batch.
Leave every article as a draft. Then create a new menu called "Help" and add
one item per category. At the end, give me a changelog listing every category,
draft, and menu item you made, with their ids.

Why this is safe to run

The first phase writes nothing. Reading your posts and categories only tells the agent what already exists, so you approve the full outline before anything is created.

When you do approve, the articles land as drafts, never published, so the agent writes the words and you decide what goes live. Each write is checked against the capability of the user you bound the agent to, and the create and menu abilities stay off until you switch them on. Every category, draft, and menu item is reversible: a draft trashes, a term or a menu item deletes, so a plan you change your mind on is easy to unwind. And every call lands in the Activity Log with the id it touched, so the changelog it hands you matches what actually happened.

Already connected? You do not have to paste this at all. Ask your agent for the “build a knowledge base” recipe, or just describe the help center you want, and it runs the same plan-then-build flow on your own site.