holistic-writing

Files (4)

• SKILL.md
• openai.yaml · agents/
• consolidation.md · references/
• reading-examples.md · references/

SKILL.md (first lines)

# Holistic writing

Write for readers without the originating conversation, investigation, or design session.
Establish the context for standalone writing or whole-artifact review, then use the shared editorial pass.

## Scope and authority

Specialized owners decide the artifact’s substance; an editorial pass does not expand permission to change it.
A review request does not authorize prose edits.
For review-only work, report findings, evidence, consequences, and the smallest useful corrections.
For authoring with no named artifact, establish the intended reader, purpose, and deliverable before drafting.
Ask when missing context would materially change the result rather than inventing its audience or authority.

When a dedicated skill owns the requested writing or review, start there rather than running this workflow separately.
Specialized owners link directly to the [shared editorial pass](references/editorial-pass.md) under their own invocation conditions.
An editorial-only request can start here when the artifact's dedicated skill does not cover that review.
Reuse established decisions rather than restarting their workflows.
For documentation-specific reader tasks, forms, prerequisites, commands, links, and workflow checks, use [Documentation](references/documentation.md).
For placement alone, use [Documentation placement](../references/documentation-placement.md); a small addition or new heading does not require this whole-artifact workflow.

Use adjacent owners only for their tasks, not as compulsory stages of this pass:

- `readme-writing` owns introductory README writing and review, not every file named README.
- `reorganize-docs` owns existing documentation trees, page splits, renames, consolidation, and navigation.
- `new-tool-development` owns its tool lifecycle and human-authored product briefs.
  Agents may review those briefs and add only the TODO comments it permits, not write or rewrite brief prose.
- `requirements-definition` owns requirements authoring from an approved product brief.
- `human-review-packets` owns selection and framing of human decision questions and approval handoffs.
- [Spec review](../spec-review/SKILL.md) audits specification contracts for consistency, traceability, unsupported restrictions, and stage-appropriate completeness.
- `skill-authoring` owns skill behavior, discovery, and procedure; this skill owns written presentation without silently changing those decisions.
- `typst` owns Typst syntax; use it when the artifact needs that markup, not for every prose review.
- `tighten-prose` owns bounded sentence- and paragraph-level polishing within an established explanation.

If an owner is unavailable, preserve its boundaries, state the limitation, and do not claim that its specialized review occurred.

## 1. Establish the artifact and context

For direct authoring or review, establish any missing reader, purpose, requirements, and factual evidence.
Use the brief, relevant entry points, authoritative inputs, and representative uses.
For creation, inspect the material the new artifact must explain and any established destination or form.

If another procedure has already established this context, reuse it.
Do not reconstruct the investigation or reopen settled design decisions.

## 2. Use the shared editorial pass

Read and follow the [editorial pass](references/editorial-pass.md) with the artifact, established context, and authoring or review-only authority.
It covers explanatory development, reading experience, factual fidelity, revision, and validation through completion.
Specialized owners retain authority over substance and behavior; this entry point does not start their workflows as compulsory editorial stages.

From jyn514/dotfiles, Unlicense.

More from jyn514/dotfiles