docs-maintainer

# Docs Maintainer Use this skill to decide whether public docs need updates and to make those updates in the right place. ## Docs Boundaries - Public website docs source lives under `docs/public/**`. - Internal product/spec planning stays under `docs/specs/**`. - Implementation plans stay under `docs/plans/**`. - Architecture decisions stay under `docs/decisions/**`. - Raw supporting notes can remain under `docs/**` outside `docs/public/**`, but do not publish them unless rewritten for users. - `docs/public/meta.json` owns published-page order and navigation groups. Page paths own routes, and page frontmatter owns titles and descriptions. - The landing/docs website generates its content from this directory. Do not hand-edit generated files in the landing repository. ## When Docs Need Updates Check public docs when a change affects: - CLI commands, flags, install commands, or runtime launch behavior. - Configuration keys, environment variables, defaults, profiles, or feature flags. - Workspaces, workflows, tasks, agents, executors, worktrees, Git behavior, or review flows. - Docker, Kubernetes, service, desktop, remote environment, or Windows instructions. - Public APIs, WebSocket messages, workflow import/export schemas, or integration contracts. - Screenshots, visible UI labels, navigation, onboarding, or user-facing terminology. Skip public docs when the change is: - Purely internal refactoring with no behavior change. - Test-only, fixture-only, or build-only withou...