Knowledge becomes wiki pages and decks

Request: „Create a wiki subpage with everything that matters about the agentic PMO, audience: executive management, with an architecture diagram.“

1. The AI reads the Business Brain: goals, architecture, milestones, decisions
2. It shapes the content for the audience and builds visuals such as the architecture diagram
3. It creates the page directly in the wiki through a deterministic script — or produces the deck or document for the document store
4. Visual review loop: render, check, correct — before a person sees the result

Status pages, decks and documents are compiled by hand from scattered sources — hours per artefact, in any organisation.

A person reads and approves the created page; tone and audience framing remain a leadership call.

Diagram nodes disappeared behind text blocks, slide titles overflowed — the rules for that now live in the skill and in the visual review loop.

Any organisation that packages knowledge into slides and wiki pages. Store the knowledge in a structured way once, and every artefact comes at the price of a prompt.

Much of PMO work is packaging: the same knowledge as a wiki page for executives, a deck for the team, a document for the review. In the agentic PMO the knowledge lives once, structured, in the Business Brain. A prompt in the code editor with a link and an audience is enough; the coding agent shapes the content, builds the architecture diagram and creates the page in the wiki through a deterministic script. Five minutes, then a person proofreads. Across decks, wiki and document store the time saved is around 80 to 90 percent. The deterministic route into the wiki, a script instead of browser clicks, keeps quality stable: same format, every time.