trails-editorial

name	trails-editorial
description	Complete Trails editorial review workflow. Use when reviewing docs, ADRs, README changes, release notes, agent guidance, or docs-heavy PRs for voice, style, structure, correctness, and readiness.
metadata	{"version":"0.1.0","author":"trails","category":"documentation"}

Trails Editorial

The v1 vocabulary families are live. Use derive for contract-owned fact production and render for surface presentation.

Run a complete editorial review for Trails documentation and prose-heavy changes. This is a workflow skill. It should work in Claude, Codex, or any agent harness that can read skills, inspect files, and run commands.

Load First

Before reviewing, load:

1. trails-writing-voice
2. trails-writing-style
3. trails-writing-docs

If one is unavailable, continue only after reading the corresponding .agents/skills/<name>/SKILL.md file directly. If the file is missing, report that as part of the review.

Inputs

The target can be:

• one file;
• a directory;
• a PR diff;
• a stack;
• an ADR draft;
• a release note;
• agent guidance;
• a question such as "is this ready to merge?"

If no target is supplied, infer the smallest relevant target from the current conversation or working tree.

Workflow

1. Establish Scope

Identify:

• target files;
• source-of-truth docs or ADRs;