Release notes effort, per biweekly release
1 workday
2 hours
Automated from Jira to published HTML, across 10+ consecutive on-time releases.
Open to remote senior technical writing roles
Documentation that scales because it's engineered to.
I'm Justin, a senior technical writer in healthcare software. I write the enterprise and developer documentation, and I build the AI tooling that keeps a 1,900-article knowledge base accurate.
10+ years in healthcare data and documentation
60+ agent skills and 3 MCP servers
Impact at MHK, 2024 to present
What changed when documentation got engineered
Knowledge base edits per year
88 edits
~1,000
The knowledge base moved from write-once to continuously maintained, with 779 new articles in 2026.
Support hours saved per year
17,500 tickets analyzed
875+ hours
AI classification traced avoidable support contacts back to specific documentation gaps.
Writing
All 14 samples
Featured samples
Sanitized documentation from enterprise healthcare systems, written for developers, implementers, and state agency teams.
Integration test plan
Medicaid EPS test plan
AWS cloud migration test strategy, ANSI X12 837 EDI validation, defect lifecycle governance, and a 13-stage MCO onboarding work breakdown.
Written for QA leads and state agency project stakeholders
Documentation governance
Configuration style guide
Authoring standard for 400+ articles: active voice, the Step/Result pattern, system variable templates, and quality checklists.
Written for technical writers and contributing SMEs
API reference
REST and FHIR R4 integration guide
OAuth2 authentication, HL7 FHIR R4 resource schemas (Patient, Encounter), rate limits, and webhook architecture.
Written for integration developers
Systems and AI
Tooling that keeps the docs honest
Multi-agent review pipeline
Agents review, score, and verify articles against a quality rubric, then publish through the Document360 API.
Jira-to-HTML release notes
JQL extraction, schema checks, and publishing, cutting each release from a day of work to two hours.
Open-source documentation tools
Public, sanitized versions of the skills, classifiers, and capture tooling I use every week.
$ doctype classify examples/docs/ --category-from-dir create-a-case T2 Task / Procedure data-exchange-faq T10 FAQ record-detail-tab T3 Field / Screen Reference 2.4-release-notes T7 Index / Landing / Rollup runbook-queue-backlog T12 Internal / Non-content 5 total
Example run from the doc-type-classifier README, trimmed to fit.
Open source
All repositories
On GitHub
21 Claude Code skills for auditing a 1,900-article documentation corpus and reviewing drafts before they reach customers. Most exist because something went wrong once.
Playwright screenshot capture for documentation, with redaction that fails closed so real patient or customer data never ships in an image.
Sorts documentation into thirteen types from HTML structure alone and explains each decision. No model, no network, microseconds per page.
Hiring for documentation or DocOps?
I'm looking for remote senior technical writing and documentation systems roles.