# Technical Writer: Clear Docs Written From What You Actually Built > The Technical Writer is the AI technical writer in the Ai1 platform by MyZone AI: from your code, tickets and change history it drafts user guides, API reference docs and release notes in plain language, links each section to its source and flags pages that no longer match your product. Canonical page: https://myzone.ai/pages/agents/ai-technical-writer-agent Part of Ai1, by MyZone AI. Book a Tech Writer walkthrough: https://calendly.com/d/ct6h-tcy-8qf/ai1-demo?a1=Technical%20Writer&utm_source=myzone.ai&utm_medium=agent-page&utm_content=ai-technical-writer-agent-final Last updated: 2026-10-15. Reviewed by the MyZone AI team. User guides, API docs and release notes, drafted from what you shipped. ## At a glance - **Works from:** Your code, tickets and change history - **Writes:** User guides, API reference docs and release notes - **Each section:** Links to the change, ticket or code it describes - **Stale docs:** Pages that no longer match the product are flagged, with updated drafts - **Before publishing:** A person who knows the feature checks every draft - **Left out:** Secrets and internal details found in code ## What the Technical Writer does - **Writes user guides:** Step-by-step guides for the features people use. - **Documents APIs:** Endpoints, parameters and examples, drafted from your code. - **Writes release notes:** What changed and why it matters, for your users. - **Links to the source:** Each section points to the change, ticket or code it describes. - **Spots stale docs:** Flags pages that no longer match the product. ## How the Technical Writer differs from developers writing docs at the end When developers write the docs after the work is done, the docs come last and often fall behind. The Technical Writer drafts user guides, API docs and release notes from your code, tickets and change history, in plain language, with each section linked to its source. It writes only what it can see, leaves secrets out and flags stale pages. A person who knows the feature checks every draft before it is published. How this differs from the Requirements Agent (https://myzone.ai/pages/agents/ai-requirements-agent): To write down what should be built, use the Requirements Agent; the Technical Writer documents what was built. ## How it works 1. **Point it at the changes** (When there is something to document): Share the code, tickets and change history it should document. 2. **It drafts the docs** (Once the changes are shared): Guides, API docs or release notes are drafted with source links. 3. **Expert review** (you approve) (Before anything is published): A person who knows the feature checks the draft for accuracy. 4. **Publish** (After approval): You publish the approved docs where your users read them. ## When to use it - **A release is going out:** Release notes written from the change list. - **Your API has no docs:** Reference docs drafted from the code. - **Users keep asking the same question:** A guide that answers it. - **The docs no longer match the product:** A list of outdated pages and updated drafts. ## What you get - User guides - API reference docs - Release notes - Source links for each section - A list of outdated pages ## Example: release documentation pack traced to its sources Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended. What it was asked: Release 6.2 ships on 22 October. Write the release notes, update the user guide and document the new API endpoint from what the team actually built, in plain language. This is an illustrative example of the documentation pack Technical Writer is being built to produce: change summary, release notes, a user guide update and an API reference page, each traced to its source. It was written by hand from the agent's design for an invented software company with invented code changes, tickets and figures. No real code, systems or people were involved, and nothing was published, changed or sent. Run date: 15 October 2026. ### What it found - All 14 changes in release 6.2 are documented across release notes, two user guide chapters and one API page, written from 38 commits, 11 tickets and 3 change notes. - All 126 statements trace to a commit, ticket or change note; three unsupported claims, including "sync is much faster", were removed or reworded. - Two questions for engineering hold back two lines: the old endpoint's removal date and whether an "on_hold" status should be visible to outside systems. ## Guardrails - Your Ai1 team will tell you when the Technical Writer is ready for your account. - Every draft is checked by someone who knows the feature before it is published. - It writes only from your code, tickets and changes, and does not guess at behaviour it cannot see. - Secrets and internal details found in code are left out. ## Frequently asked questions ### Who are release notes written for? For the people who use your product, not the people who built it. Good release notes say what changed and what it means for the reader. The Technical Writer writes them from your changes in plain language. ### What belongs in API reference documentation? Each endpoint, the parameters it accepts and an example, written so a developer can use it without reading the code. The Technical Writer drafts these from your code, links each section to its source and has someone who knows the API check the draft before it is published. ### How do product docs fall out of date, and how do you catch it? Every release can change a screen, a setting or a step that a guide still describes the old way. The Technical Writer links each section to the change or ticket it came from and flags pages that no longer match the product, with updated drafts for review. ### What does an AI technical writer do? It drafts user guides, API docs and release notes from your code, tickets and changes. The Technical Writer writes in plain language and links each section to its source. ### Who checks the docs are accurate? A person who knows the feature reviews every draft before it is published. ### How is it different from the Help Center Writer? The Help Center Writer writes help articles from customer questions. The Technical Writer documents your product from its code and changes. ### How is it different from the Requirements Agent? The Requirements Agent writes what to build. The Technical Writer documents what was built. ### Is the Technical Writer available now? Not yet. Your Ai1 team will tell you when the Technical Writer is ready for your account. You can talk to us today about the docs your product needs. ## About Ai1 Ai1 is the AI operations platform by MyZone AI, where each client runs on its own private server. The Technical Writer is not sold on its own: every Ai1 agent, including this one, is included on Developer Pro and every Fully Managed option, with no per-agent charge. Developer Core includes the development agents. Pricing: https://myzone.ai/pages/services/ai1-pricing. Security: https://myzone.ai/pages/security.