Editor Test

The linters measure mechanics. This test measures the writing, and it only measures anything if the judge has not seen the research: a fresh sub-agent gets the draft, the style guide, the reference page, and the shape the page's type follows, and nothing else.

Procedure

1. Agree the dispatch with the owner before sending anything: how many judges, and what each reads. A page written or rewritten whole gets its own judge, unless several pages were drafted as one topic and the marks need the cross-page view, in which case one judge reads the set. A round that changed parts of pages sends the touched pages to one judge, each with its changed sections named, or to several judges split by topic when the set is large. Pages of different genres go to different judges, because the reference page differs. One judge per page is a choice, not the default. When no reviewer is in the session, state the dispatch in the report or PR description and proceed.
2. Dispatch the fresh sub-agent(s) (subagent_type: general-purpose) with the template below, filling {DRAFT} (absolute path), {STANDARD} (the style guide's path), {EXEMPLAR} (the reference page in the draft's genre: en/cloud/use-dify/build/new-agent/overview.mdx for a concept page, en/cloud/use-dify/build/new-agent/build.mdx for a task page or a reference), {SHAPE} (the pack's page-shape or conventions for this document type, as a path or a path with a section name, path § Section: the CLI pack's SKILL.md § Page shape, the API pack's references/spec-conventions.md, the env-var pack's SKILL.md § Document Structure; for a page with no pack, the line reads "none"), and {CHANGED} ("the whole page", or the sections and paragraphs this round changed, named as the reader would find them). When one judge reads several pages, the page block (files 3 and 4 and the changed line) and the reply repeat per page, under the page's path. The shape file keeps the judge from marking a required table or synopsis as a fault; the language inside the structure is still judged. Put nothing else in the prompt: no fact sheet, no research, no account of what changed beyond that line, no concerns of your own.
3. Relay the report unedited. Then act on it. The verdict judges this round's work. "Ship with light edits": fix the marked sentences. "Needs heavy edits": rewrite the marked units whole, from their job. "Needs rewrite": hand the draft and the marks to a fresh drafter, as the pipeline's Write stage does for a changed idea. After either rewrite, dispatch a new judge; never send a revised draft to the same one. Marks outside the change are the page's standing debt: report them to the owner as a list with a proposal for each (fix in this round, or a follow-up), and touch none of them without that decision, because on a release branch a page's debt is not this round's scope.

Dispatch prompt

You are the editor of a documentation set, reading a draft the way its owner
would before deciding whether it can ship.