odoo-doc-site

Role

Front door for writing or updating the pages of a product documentation site kept in its own repository: one branch, one worktree and one pull request per series. Audience: the site's readers (roles and audience come from the site row). It launches odoo-doc-site-writer per disjoint page group.

Out of Scope

• Docs that ship inside a module (doc/index.rst, the App Store page) -> odoo-doc-illustration
• Marketing copy, blog, landing text -> odoo-content-draft
• A video or GIF of a workflow -> odoo-demo-recording
• The catalog, role map or walkthrough alone -> odoo-doc-feature-map
• Rating a screen -> odoo-ui-review; fixing a branding gap in module source -> odoo-coding
• Merging the PR or watching it to merge -> odoo-pr-monitoring
• Porting pages from a lower series to a higher one -> odoo-forward-port (its docs-site lane invokes this skill with WORKTREE and LAND: caller)

Inputs

SITE (key or repo), SERIES (one or several; each is its own worktree, branch and PR), the AREA (app cluster) or a module list, an optional page list, and these optional inputs:

• FROM CHANGE - the path of a change file (<ISOLATE_DIR>/docs/change-<slug>.md) when this skill is the tail of a code change: one line per changed user-visible feature with its module and UI label. Read it; the plan then holds only the pages and shots those features touch.
• CODE_WORKTREE - absolute path of the code being documented. As a plan tail node it is <code repo>/run-integration. Absent: the catalog row's addons path.
• RUN_ID - the caller's run id. Standalone: make one per series.
• INSTANCE_HANDLE - optional: a demo build the caller already holds (the module-docs step's, or an i18n export build). When its series is the target, demo is true, languages_loaded holds every site language and its addons_path covers CODE_WORKTREE (else the catalog addons), step 3 installs the plan's missing modules on that lease by a delta init and provisions nothing (${CLAUDE_PLUGIN_ROOT}/snippets/docs-after-change.md § One capture instance); the caller releases it.
• WORKTREE with LAND: caller - a caller that owns the branch (odoo-forward-port) hands the series worktree in: step 0 creates no worktree and no branch, steps 7-8 run nothing, and the return carries the file list for the caller to commit. It may add PAGE PLAN, the rows it decided (work: port for a page to re-verify on this series, skip for one forwarded as it is): step 1 keeps those rows, adds only the skip rows of pages an open pull request already covers, and presents no gate.