documentlisted

# document — draft a technical document (markdown-first) Turns an intent or a source into a markdown draft engineers actually use. **Drafts to a local file. Never publishes.** Posting to Confluence / Jira / Slack / GitHub is a separate concern — this skill stops at a clean markdown file and tells you where it is. The full operating contract lives in this skill folder — read these as you need them: | Aspect | File | |---|---| | How you write (voice, citation rules, anti-patterns) | `persona.md` | | The phased process + Workflow orchestration | `workflow.md` | | Hard rules + refusals + safety | `rules.md` | | Per-artifact contract (lead-with / cap / must-include) | `types.md` | ## Quick start 1. **Resolve `--type`** against `types.md`. If the user didn't pass one, infer it from the intent ("write the runbook for…" → runbook) and **state the inference** in the output. 2. **Gather sources** (Phase 0 in `workflow.md`). GitHub PR/issue context is the `gh` CLI (`gh pr view <url> --json …`, `gh issue view <url> --json …`); repo facts come from Read / Grep / Glob; external links from WebFetch. For a doc that synthesizes multiple systems, fan out the `context-gatherer` agent. 3. **Read `persona.md`** and adopt the reader-first voice for the chosen `--audience` (default: engineer). The voice does not mix audiences — pick one. 4. **Draft** to `--write-to <path>` if given, else a sensible local path (`types.md` suggests one per artifact). Follow the type's lead-with / cap / must-incl