About
Gaurav Trivedi — technical writer, AI tinkerer, slow-writing advocate.
👋 Hi, I’m Gaurav
I’m a Principal Technical Writer at Red Hat. I maintain open-source documentation at enterprise scale. OpenShift Dev Spaces, OpenShift Docs, the kind of docs that ship with products millions of people depend on.
And I’ve spent the last year trying to automate myself out of that job.
Not because I hate it. Because I wanted to know: what happens when you actually succeed?
Why this blog exists.
I’ve been a technical writer for over a decade. The last few years have been spent at the seam between documentation and AI tooling — building, breaking, and writing about what’s changing. This site is the working journal.
Here’s what you’ll find:
- Long-form essays on AI, craft, and the future of technical communication.
- Tooling teardowns — Claude, Cursor, Gemini, NotebookLM, and the workflows that survive past a week.
- Honest reflection on what the AI shift looks like from inside a working team.
Here’s what I built.
Every repetitive thing I used to do by hand, I turned into tooling. Editorial review. Quality scoring. Content planning. Style compliance. All of it.
| Repo | What it does |
|---|---|
| redhat-docs-agent-tools | Claude Code skills and agents that orchestrate the entire Red Hat doc workflow. Requirements to review, end to end. |
| cqa-assessment | Scores docs against all 54 CQA 2.1 quality parameters. Vale + DITA compliance, automated reporting. |
| content-editorial-assistant | AI editorial system with REST + WebSocket APIs and architecture diagrams. |
| productivity | Productivity tracker with cognitive load classification and streak gamification. |
These aren’t prototypes. They run against real documentation pipelines, on real content, every day.
So what happens when you automate your own role?
You start seeing the layer above it. The architecture. The systems design. The part where someone decides how the models, the data pipelines, and the human endpoints connect.
That’s the job I’m building toward now. And I’m documenting the entire pivot in public, because no one else is:
| Repo | What it is |
|---|---|
| The Syllabus | A 365 day gamified curriculum to go from Technical Writer to AI Solutions Architect. Four seasons. One year. No shortcuts. |
| The Logs | The day by day record of actually doing it. Wins, dead ends, and unedited tape. |
The foundation.
The day job isn’t something I’m leaving behind. It’s the reason any of this works. You can’t automate what you haven’t mastered.
I write about what this transition actually looks like at beingtechnicalwriter.com. Not theory. Not predictions. What’s happening right now, from inside the machine.
This page is a living document. If you came back and something changed, that's the point.