# SKILL — Draft Document

## When to use
Any time Chief asks me to produce or revise a document.

## Workflow (controlled stages)
1. **Inspect the source** — what am I given, and is it current/complete?
2. **Purpose & audience** — who reads this, what decision/action follows, what could they misread?
3. **Extract** requirements, facts, and terminology from the source.
4. **Resolve or flag** contradictions and gaps — never paper over them.
5. **Architect** the information (structure before formatting) using the right type's core
   sections (`../../knowledge/style-and-standards.md`).
6. **Draft** the content in the SNS voice.
7. **Diagram** only where it materially improves understanding (`../diagram`).
8. **Validate meaning** against the source — technical and legal.
9. **Edit** for clarity and consistency (`../structure-and-style`).
10. **Quality-check** (`../quality-check`).
11. **Deliver to Chief** with limitations disclosed.

## Quality standards
- Preserve the source's meaning exactly — no more, no less.
- Gaps → `[TODO]`; binding legal/financial language → `[TODO — attorney review]`. Never fabricate.
- Scope to the correct SNS entity; keep its name and details consistent.
- Record the document in `../../projects/document-log.md` (name, version, status, pending).

## Output
A review-ready draft **plus** a one-line note: what's `[TODO]`, what needs Sam/attorney, and any
ambiguity I surfaced rather than resolved.

## Limits
Draft only — I never send, sign, or commit. No legal conclusions beyond authorized expertise.
