AI for technical writing
Ultramarine Work drafts API reference pages from the OpenAPI spec, writes release notes from merged PRs and assembles O&M manuals with Z535.6 safety messages, from the files your SMEs and dev teams already keep.
Pump-station-OM-manual.docxExampleDeer Creek Pump Station Operation and Maintenance Manual
6.1 Before you begin
Removing a pump takes two qualified operators, the station lockout kit and the 2-ton davit crane. Pump P-2 can come out while P-1 stays in automatic service. Check that the HMI shows the wet well below 3.0 feet before you open the hatch.
6.2 Lock out pump P-2
DANGER: Hazardous voltage. Contact with energized parts will cause death or serious injury. Set the P-2 selector switch to OFF, open breaker CB-2, apply your lock and tag, and test for zero voltage at the motor leads before you disconnect the cable.
CheckedThe as-built single-line shows CB-2 feeding P-1, so confirm the breaker number at the station.
How it works
- 1
Load the docs folder
Put in the SME notes, the PRD, Jira ticket exports, the OpenAPI spec, merged-PR descriptions, vendor manuals, as-built drawings, screenshots, the style sheet and the termbase. Any format works: Markdown, Word, PDF, HTML or CSV.
- 2
Ask for the deliverable
Request a reference page from the spec, the 4.2 release notes from the PRs, the pump-station O&M manual from vendor literature, a taxonomy rebuild or the WCAG audit. It writes in your house style and cites the file behind every claim.
- 3
Check it against the product
Run every command and click the buttons to confirm the steps work in the current build. Models get real defaults wrong more often than they invent features, so trace each statement to its source file. Publish nothing you have not checked.
Ask it for
“Draft the O&M manual for the Deer Creek pump station from as-builts, Halstead pump literature and commissioning records, with Z535.6 safety messages.”
Pump-station-OM-manual.docx“Check the safety messages against ANSI Z535.6, flag panels missing a signal word, hazard, avoidance or consequence, and any NOTICE panel with the alert symbol.”
OM-safety-message-review.pdf“Write reference pages for the /refunds and /disputes endpoints from the OpenAPI 3.1 spec, with request and response examples and a table of error codes.”
Payments-api-reference.md“Compile the 4.2 release notes from merged PR descriptions and the git log export, grouped as Added, Changed and Fixed, and call out what the PRs never explain.”
Release-notes-4.2.docx“Turn our support tags into a controlled vocabulary: pick preferred terms, write scope notes, make the BT, NT and RT links, and list the near-duplicate terms.”
Support-taxonomy.xlsx“Audit the help-center HTML export against WCAG 2.1 AA, list what fails each success criterion with its severity and the fix, and draft the VPAT 2.5 remarks.”
Help-center-VPAT-draft.docx
Inside the Technical Writing mode
Operations and maintenance manual
Builds an O&M manual from OEM literature, as-builts and commissioning records, with procedures, maintenance schedules, spares lists and Z535.6 safety messages.
Taxonomy and information architecture
Rebuilds the team’s tag list as a controlled vocabulary, with preferred terms, scope notes and BT/NT/RT links, and flags the near-duplicate terms.
Accessibility audit
Checks content exports against WCAG AA, reports issues by success criterion, severity and fix, and drafts the VPAT remarks you complete as the ACR.
- Office skills
- Excel, Word, PowerPoint, PDF
- Tools
- Read, edit and write files, Search files, Run code, Search and read the web, View images
- Connectors
- SharePoint, Google Drive, Gmail, and additional custom connectors
- House style
- Your fonts, layouts and rules, on every file
Who it’s for
Technical writers, documentation specialists, API writers and information developers for software, hardware and plant systems, through documentation managers.
Questions
Will it invent features or steps our product doesn’t have?
It can, which is why the mode’s skills tell it to cite the source file for every claim and say what it couldn’t find instead of guessing. Docs agents misstate real defaults more often than they invent features. The DoGBench audit of 1,267 submissions found technical inaccuracies in 36.6% and fabricated content in 6.1%. Follow the draft through the build and check what it says against the interface before anything ships. That review stays with you and your SMEs.
Does it follow our style sheet and use our termbase?
Yes, once the style sheet, the term list and a past manual are in the folder and you point it at them. Those files set the standard, from heading structure down to the words you have banned. Ask it to review a chapter against them and it reports the violations with a suggested fix for each, rather than rewriting the text on its own.
Can it draft the safety messages in an O&M manual?
Yes, it drafts them with the signal word, the safety alert symbol where the standard requires it, the hazard, how to avoid it and the consequence of ignoring it. The draft places them as grouped, section or embedded messages. Choosing the signal word stays with you. DANGER, WARNING and CAUTION mark different injury severities, and NOTICE covers property damage and takes no alert symbol. Engineering owns the hazard analysis, so you confirm every level before the manual ships.
Does the accessibility audit replace screen reader testing?
No, and it is not a substitute for the manual testing your evaluation methods must document. The audit lists every issue, the success criterion it fails, its severity and the fix, and writes up the VPAT remarks. A defensible ACR also documents how you tested: screen-reader sessions, keyboard-only navigation, zoom to 200% and 400%. Procurement teams read the evaluation methods section first, and scan-only reports get discounted.
Where does our unreleased product data go?
Ultramarine Work changes files only in the project’s folder. When a request needs it, it can read files elsewhere on your computer, never passwords, keys or app data, and you can turn that off in settings. The model runs on Paper Instruments’ servers, so the content it works on is sent there to be processed. Paper Instruments is SOC 2 Type II, and our security and compliance details are on our compliance page. Whether that fits your NDA for prerelease material is a call for you and your legal team.