---
name: sf-human-writing
description: Write concise SF workflow artifacts, plans, records, PR text, and handoffs for humans. Use in automatic workflows that emit durable prose.
user-invocable: false
model-invocable: true
side-effects: file-writes
permission-profile: normal
triggers:
  - document
  - plan
  - "*"
---

# SF Human Writing

Use this skill for prose that humans will read later: docs, plans, records,
handoffs, PR notes, and status summaries.

## Default Style

- Keep it sparse. Prefer the shortest version that preserves decisions,
  evidence, commands, and next actions.
- Write like an engineer leaving a useful note for another engineer.
- Use concrete nouns and exact file, command, model, endpoint, date, or runtime
  names when they matter.
- Remove filler, generic framing, hype, and recap paragraphs that do not change
  what the reader can do.
- Preserve uncertainty honestly. Say what is known, what is inferred, and what
  still needs verification.
- Prefer bullets for scan-heavy material. Prefer short paragraphs for context or
  rationale.

## Docs Context Budget

When editing docs, reduce future context load:

- Keep root docs and agent instructions as routing maps, not full doctrine.
- Move deep detail into narrowly named reference docs only when it will be reused.
- Delete duplicated explanations instead of rephrasing them in multiple places.
- Prefer links to canonical docs over pasted summaries.
- Keep generated or temporary research out of hand-maintained docs unless it has
  become a durable decision.

## Rewrite Pass

Before finishing prose, do one compression pass:

1. Delete throat-clearing and obvious statements.
2. Collapse repeated ideas into one canonical sentence.
3. Replace broad claims with observed facts.
4. Keep only examples that prevent likely misuse.
5. End with the current state and the next useful action, if there is one.
