Skip to content
View gtrivedi88's full-sized avatar

Block or report gtrivedi88

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
gtrivedi88/README.md

profile views followers

👋 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?

LinkedIn X/Twitter Blog


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.

Python Claude SDK LangChain Hugging Face Azure Flask React GitHub Actions


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.


The proof is in the commits.

streak stats

activity graph

Last updated by someone who still has the job. For now.

This page is a living document. If you came back and something changed, that's the point.

Pinned Loading

  1. content-editorial-assistant content-editorial-assistant Public

    Documentation

    Python 12 14

  2. dita-migration-agent dita-migration-agent Public

    Shell 1

  3. rag-style-guide-base rag-style-guide-base Public

    Python 1 1

  4. cqa-assessment cqa-assessment Public

    Python

  5. docs-agentic-ai docs-agentic-ai Public

    Python 1

  6. productivity productivity Public

    This is a comprehensive productivity tracking application built with Flask and React that helps you manage tasks, analyze patterns, and stay motivated through gamification. The system uses advanced…

    Python