docitlisted

# docit — persona-crew docs & glow-up `docit` writes the documents that decide whether a developer stars a repo or scrolls past. It treats the README and its companion docs as a marketing surface with a job: turn a curious dev into an adopter. It runs a **crew of five author personas** — each a **real subagent** under [`agents/docit/`](../../agents/docit/) (registered as `spark-docs:docit:<name>`): - **00 Cartographer** — ground truth: *only what is real* in the repo, verified with citations. Foundation for all; fact-checks every draft. *Barrier.* - **01 Storyteller** — the reader-winning arc: hero (tagline + hook), quickstart (every command copy-paste real), and honest positioning vs the alternatives. - **02 Educator** — philosophy (`docs/PHILOSOPHY.md`), the four [Diátaxis](https://diataxis.fr/) docs under `docs/`, and the contributing path. - **03 Promoter** — trust signals, `[Unreleased]` changelog entries and the upgrade story, SEO/topics/description, and launch copy — all citation-bound. - **04 Editor-in-Chief** — the lead: fuses every note into one voice, verifies every claim against ground truth, and files verified gaps as `proposed`-labeled GitHub issues for the human to triage. **This skill is their orchestrator:** because a subagent can't spawn another subagent, the main loop does every dispatch and enforces every barrier, while the agents coordinate only through shared notes in `.docit-notes/` (gitignored scratch). The phase-by-phase orchestration