editorial-context

Installation
SKILL.md

Editorial Context

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.

Check for Existing Context

Before asking questions, check these sources in order:

  1. 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.
  2. .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.
  3. Neither exists: Work through the questions below to build context from scratch.

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.

Context-Gathering Workflow

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.

1. The Work

Installs
4
GitHub Stars
1
First Seen
Mar 22, 2026
editorial-context — brycehamrick/editorial-skills