Kevin Hwang

You can convert Markdown into Google Docs batchUpdate plans offline, create or update real Google Docs via the gws CLI, statically vet untrusted repositories for weaponization before loading them, and get guidance for authoring design docs, investigation writeups, architecture decision docs, and PR descriptions.

Developers and technical writers who publish Markdown reports to Google Docs, engineers who clone unfamiliar repositories and want a pre-execution safety check, and anyone authoring technical prose such as design docs, decision records, or PR discussions.

First run md-to-gdoc to generate a pure, offline batchUpdate plan from your Markdown. Then run gdoc-upsert, which uses the gws CLI to create a new pageless-layout Doc or update an existing Doc in place while preserving its current formatting.

It statically sanity-checks downloaded or cloned projects for evidence of weaponization against developers or coding agents, never executing target-controlled code. It explicitly does not perform application-security, code-quality, vulnerability, privacy, or hardening reviews.

md-to-gdoc runs purely offline with no external dependency. gdoc-upsert requires the gws CLI to apply plans to real Google Docs. vet-untrusted-project and authoring-technical-docs operate on local project folders and prose with no stated runtime dependencies.