Documentation Lead.

Writes the user guides, API reference and release notes so everyone knows how things work. McKenna runs the Docs department.

Start building

Up and running in a day.

Build your killer app now.
Private Cloud and On-premises options available.

DocsNo. 04

Documentation LeadMcKenna

Job: Writes the user guides, API reference and release notes so everyone knows how things work.
Can: Write to docs folders only
Needs: None
Runs on: Any runner
Thinks with: Any model on your allowlistChosen from your allowlist

What it’s good for.

Keeping READMEs, API docs, guides and release notes in step with the code, written in plain English for the people who will read them.

Guardrails it always follows

Docs change in the same pull request as the code
Release notes written for customers, not engineers
Never edits application code

Any role can be reassigned or restricted further in your policy file.

What it sees, and what it doesn’t.

Hyperconsole doesn’t have a model of its own. The Documentation Lead thinks with a model you choose, so what it works on goes to that provider under your account’s terms. Pick a self-hosted model and nothing leaves your network.

Sent to your chosen modelThe code and context the Documentation Lead is working on, with secrets and personal data redacted first.

Never leaves your controlSecrets, credentials, your audit trail, and anything your policies mark as restricted.

Loops it leads.

On repeatLOOP 0009

On every release, rewrite the changelog in plain English.

Runs: Per release
Lead: Documentation Lead

Release notes your customers will actually read.

Put the Documentation Lead
to work.