Use at the start of any editing project to create or update the shared editorial context document. Also use when the user mentions "set up the project," "capture the context," "who is the audience," "what style guide are we using," "start editing," "new project," or wants to avoid repeating foundational information across editing sessions. Creates .agents/editorial-context.md that all other editorial skills read automatically. Run this first before using editorial-structural, editorial-development, editorial-line, editorial-copy, or editorial-proof.
This skill establishes the shared context for an editing engagement. It creates .agents/editorial-context.md, which all other editorial skills read before beginning work — so you never have to repeat yourself about the audience, the style guide, the author's voice, or the project goals.
Before asking questions, check these sources in order:
PROJECT.md — If this file exists in the project root, read it first. It is the primary project context in GSD-managed projects and contains the project description, goals, audience, and scope. Treat it as authoritative and do not ask questions already answered there..agents/editorial-context.md — If this file exists, read it. Summarize what's there and ask if anything needs to be updated for the current project or session.When both files exist, merge them — PROJECT.md is the source of truth for project-level facts; .agents/editorial-context.md holds editorial-specific decisions (style guide, voice notes, issue history) that accumulate during editing.
Work through these sections conversationally. You don't need to ask every question — use judgment about what's relevant for the project type. A short essay needs less setup than a book manuscript.
Save the completed context to .agents/editorial-context.md using this structure:
# Editorial Context
## The Work
- **Title/Working title:**
- **Type:**
- **Subject:**
- **Length:**
- **Stage:**
## Audience
- **Primary reader:**
- **Knowledge level:**
- **What they want:**
- **Publication context:**
## Voice & Tone
- **Author's voice:**
- **Formality:**
- **Tone:**
- **Voice notes:**
## Style Guide
- **Guide:**
- **Key decisions:**
- **Exceptions:**
## Project Goals
- **Purpose:**
- **Success looks like:**
- **Call to action / thesis:**
## Editing History
- **Stages completed:**
- **Key decisions:**
- **Outstanding issues:**
## Author Preferences
- **Specific concerns:**
- **Areas to watch:**
- **Off-limits changes:**
Context can be updated at any point during the editing process. When a new decision is made — a style exception adopted, a structural change agreed upon, a stage completed — update .agents/editorial-context.md to reflect it. All subsequent skills will pick up the updated state.
Once context is established, the editing workflow proceeds in this order:
Note on stages 5–6: If the project is not a print book (e.g., a web article, white paper, or essay), skip editorial-typesetting and latex-book entirely. Go directly from editorial-copy to editorial-proof using the copy-edited document as the proof source.