validate-doc

Provide the artifact path, an ordered focus list, an iteration number, and optionally a review directory. The skill dispatches one review-doc subagent per focus in parallel, each writing an rNN-{focus}.md file, then returns a summary of results.

The skill globs existing rNN-*.md files in the review directory, takes the maximum NN plus one as the base (or 1 if none exist), and assigns consecutive numbers to each focus in input-list order. Any filename collision aborts the whole batch.

Conventional baselines are accuracy, architecture, depth, dx for create-spike; accuracy, architecture, integration, dx, scope for create-plan; and accuracy, comprehensiveness, clarity for archive-project. Callers may extend or trim the list per chapter.

The failed focus is recorded with status errored and its error message in the returned summary. The skill never retries, auto-bypasses, or silently swallows errors; the calling skill or captain decides whether to retry, skip, or stop.

No. The only subagent type dispatched is review-doc, which reads the focus brief and adopts the named persona's lens internally. Dispatching persona agents directly is an explicit failure mode the skill forbids.