# How to use the content writer agent - Handbook

We built an agent that automatically drafts docs PRs in [`posthog.com`](https://github.com/PostHog/posthog.com) when your code changes are merged into the [`posthog`](https://github.com/PostHog/posthog) monorepo.

The content writer agent leverages the Inkeep platform to index and reference the PostHog website, codebase, and our [docs style guide](/handbook/wizard-and-docs/docs-style-guide.md), so its drafts are usually a solid starting point — but they still need your review for technical accuracy.

## Who owns what

**Product engineers** [own the docs](/handbook/wizard-and-docs/docs-ownership.md) for their products. When the agent opens a docs PR based on your merged code, you're responsible for reviewing it for technical accuracy, iterating on it until it's right, and merging it. You don't need docs team sign-off — treat it like any other PR for your product.

**The[](/teams/wizard-and-docs.md)**

**[](/teams/wizard-and-docs.md)**

**[

](/teams/wizard-and-docs.md)**

**[Wizard & Docs Team

Wizard & Docs Team](/teams/wizard-and-docs.md) team** does not review every docs PR. Engineers loop us in when they want a second opinion. We're responsible for building the system, monitoring its output quality over time, and tuning and steering the agent.

![Agent system](https://res.cloudinary.com/dmukukwp6/image/upload/w_2000,c_limit,q_auto,f_auto/pasted_image_2026_02_20_T15_28_26_049_Z_07aa633ea5.png)

Agent system for the content writer

## The workflow

When you merge a PR in the `posthog` monorepo, the Inkeep bot automatically opens a docs PR on `posthog.com` and tags you as a reviewer. From there:

1.  Review the draft for technical accuracy, completeness, code examples, and links.
2.  Iterate until the docs are correct. See [how to make changes](#how-to-make-changes).
3.  (Optional) Loop in the docs team if you want a second opinion on style, structure, or information architecture — tag `@team-wizard-and-docs` as reviewers.
4.  Approve and merge when the docs are ready.

![Inkeep docs PR](https://res.cloudinary.com/dmukukwp6/image/upload/q_auto,f_auto/pasted_image_2026_02_20_T15_46_55_337_Z_ea3dfc42d6.png)

If you tagged `@inkeep` or made changes to the PR, a feedback form is posted after merge. This helps us understand where the agent fell short — please fill it out so we can continue improving the agent.

## How to make changes

You can iterate on an Inkeep docs PR in a few ways:

-   Tag `@inkeep` in a PR comment to ask the agent to make specific changes. Describe what you need and Inkeep will push updated commits.
-   Edit the files yourself — either by pulling the branch locally or directly on GitHub. This bypasses the AI loop entirely and is often faster when you know exact changes you want to make.

![Tag the agent](https://res.cloudinary.com/dmukukwp6/image/upload/q_auto,f_auto/pasted_image_2026_02_20_T15_36_45_867_Z_c00d06aae5.png)

## What to check

-   **Technical accuracy** — Does the documented behavior match what your code actually does?
-   **Completeness** — Are all user-facing changes covered?
-   **Code examples** — Are snippets correct, realistic, and using PostHog conventions?
-   **Links** — Do internal links (website or in-app) point to real pages?

## When to loop in the docs team

You don't need our approval to merge a docs PR. But do loop us in when:

-   You need a second pair of eyes on information architecture choices (e.g., new sidebar sections, new landing pages, navigation changes, etc.)
-   You want a style or structure review beyond what you can assess yourself
-   The change is large and you want a second opinion

Tag `@team-wizard-and-docs` as reviewers on the PR, and we'll help out.

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better