Docs gardener & API doc writer
On the schedule you choose, the agent diffs shipped changes against the docs, drafts the reconciling updates and API endpoint docs typed to the real response, edits for clarity, and drafts a PR — so docs never silently drift from the code.
What it installs
Agents 1
-
Docs Agent
Reconciles docs with shipped changes, writes API reference, and drafts a pull request.
Workflows 1
-
Garden docs
Diff changes against docs, draft the reconciling updates, edit, self-review, and draft a PR.
Goals 1
-
Docs never stale
Documentation stays in sync with what the code actually does and reads well.
Skills 3
-
document-api-endpoint
Document and type an API endpoint against its real runtime response: confirm actual behaviour, correct type drift, be precise about nullability, reuse the canonical type, and migrate legacy reference docs whole. Adapted from getsentry/skills/document-api-endpoint.
-
doc-coauthoring
Write and maintain technical documentation for a real audience: pick the right document type, lead with what matters, show with examples, link rather than duplicate, and keep it current. Adapted from anthropics/knowledge-work-plugins/documentation.
-
edit-article
Edit technical prose by ordering sections to respect their dependencies, then rewriting each for clarity, coherence, and flow with tight paragraphs. Adapted from mattpocock/skills/edit-article.
Schedules 1
-
Garden docs
Reconciles docs with shipped changes on the schedule you choose.
Requirements
What this template expects to do its job. Task Machine does not verify these — you decide whether your setup is ready.
- Connected repository — Needs a connected code repository so the agent can diff shipped changes against the documentation, confirm endpoint behaviour, and open a documentation pull request.
Get started
Install Docs gardener & API doc writer and run it with approvals.
Join the waitlist and we will send early access when the first private beta spots open.
Private beta. We invite teams in batches and never share your email.