Writing Standards
Overview
The reference layer, not the desk. One leaf maps the domain's standards, style guides and reporting guidelines: names, editions, dates, what each governs. One leaf holds the lifecycle frame — the editorial sequence, and which passes may change meaning — with done criteria per stage. This skill names authorities and finish lines; it never says how to do the writing.
When to use
- "Which style guide exists for this" and "which edition is current" questions.
- "What does standard X say" questions about the mapped standards.
- Setting done criteria for a document stage or a Definition of Done for a pipeline.
- Lifecycle questions: where a pass sits, which passes may change meaning.
When not to use
- Performing the brief, the outline, the draft, any revision pass, the copyedit, the proofread or the publish — those are craft tasks outside this skill.
- Choosing between craft procedures for a specific document — outside this skill.
Precedence
The deepest loaded instruction governs its uniquely-claimed scope; every
scope:string is claimed by exactly one file in this tree; no leaf may widen a prohibition declared by an ancestor — leaves narrow, never override upward.
Subskill index
| Leaf | Task | Trigger |
|---|---|---|
subskills/standards-map.md |
Standards, guides, editions, dates | "which style guide exists for this" |
subskills/definition-of-done.md |
Editorial sequence; done criteria per pass | "which editorial pass changes meaning" |
See also
subskills/standards-map.md— the authorities.subskills/definition-of-done.md— the frame and the finish lines.