/rota-docs
Scaffold, update or reorganize the public docs.
When to use
Use on “update docs”, “scaffold the docs”, “sync the docs with recent changes”, “restructure the docs”, or “/rota-docs”.
Reach for another skill when
- the point is a gotcha for future sessions, not user-facing documentation:
/rota-learn - you want release notes and a tag:
/rota-release
After-work mode is on. Checking docs against changes since the last `docs:` commit. Proposed updates: docs/usage/running-work.md add the new --preview note Apply these doc updates? Apply all / Apply selectively / Skip / Cancel
- doc pages under docs.path, only after you approve
- a docs: commit that marks the next after-work baseline
Flags and modes
restructure- audit and reorganize the docs tree; follows autonomy.level
(no argument)- first-run scaffold if docs.path is missing or empty, else after-work proposals
Details
Maintains the public docs. After-work mode may run in any agent, including a round worker’s PR; scaffold and restructure follow autonomy.level and escalate to the maintainer in a round. Scaffolds <docs.path>/ on first run (discovery, a tailored tree, interactive approval), proposes doc updates in after-work mode, or audits and reorganizes in restructure mode (/rota-docs restructure). Runs inline at ship time when docs.afterWork: true and the post-cycle trigger condition matches.
/rota-ship --docs is a deprecated alias for one more release: it prints a one-line pointer to /rota-docs and runs it.