document-features

Write feature documentation for the repository — one populated <docs-dir>/features/<slug>.md per requested feature — by dispatching subagents in parallel so an "all" run does not serialize. The agent docs directory (<docs-dir>) is discovered in Phase 1; it's typically agents-docs/ but setup-agentic-repository may have written it somewhere else.

This skill is the documentation counterpart to find-features. find-features discovers what is missing; document-features is the focused worker that actually fills the template, in parallel, for the features the user names.

If the user asks "find and document everything", you can start with find-features to build the candidate list, then hand that list to this skill. If the user already knows which features they want (e.g. "document auth and billing"), come straight here.

Phase 1 — Verify prerequisites and locate the docs directory

Confirm the repo has been initialized with the Mimas template, and discover where its agent docs actually live. setup-agentic-repository writes the agent doc tree to agents-docs/ by default (a sibling of any human-maintained docs/), but --docs-dir <dir> can override that (e.g. docs/agents). Don't assume the path; discover it.