Docs gardener & API doc writer

Docs gardener & API doc writer quality team

The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.

Garden docs

Diff changes against docs, draft the reconciling updates, edit, self-review, and draft a PR.

Docs never stale

Documentation stays in sync with what the code actually does and reads well. Success looks like: Each run lands an approved PR that reconciles every doc delta with shipped changes, with API reference typed to the real response and no stale claims remaining.

Garden docs

Reconciles docs with shipped changes on the schedule you choose. ## Professional quality control Objective: complete the recurring Docs gardener & API doc writer operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Inspect the repository and actual diff, reproduce the behavior, run the declared tests and checks, cover known success and error paths, and verify security, performance, migration, and rollback implications where relevant. Never infer a passing command. Technical prose must cite command output and avoid generic AI phrasing or claims that the code does not prove. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.