Automating Support Documentation

A few people asked so I open-sourced the doc-from-chats skill in majr’s agent-services repo, alongside the /wind-down and /good-morning routines already published a few weeks ago.

tldr: writing documentation is tedious and error prone when it’s done after-the-fact. When I work with an agent, docs become part of how we code. I run /doc-from-chat and it sweeps the session for what a customer would care about, verifies each claim against the actual code and writes the docs in place. Support docs get plain English; architecture notes go to an internal folder.

Claude Code has a plugin marketplace, so it’s two commands:

/plugin marketplace add majrdotapp/agent-services
/plugin install doc-from-chat@agent-services

Any other agent that reads SKILL.md (Codex, Cursor, Amp, your own harness) needs no marketplace at all. The skill is one plain markdown file. Clone the repo and copy the folder into wherever your agent discovers skills:

git clone https://github.com/majrdotapp/agent-services.git
cp -R agent-services/plugins/doc-from-chat/skills/doc-from-chat <your agent’s skills directory>

For Codex that’s ~/.agents/skills; check your agent’s docs for its equivalent.

Then run /doc-from-chat at the end of any session where something got explained. It’s MIT-licensed. The whole skill is one readable markdown file.