Publish Markdown from AI coding agents

The problem

The agent demo

Tell the agent to publish when it's done. The conversation ends up looking like:

# User: "Plan the auth migration. Publish the doc when done."

# Agent (after writing plan.md):
$ opendocs publish plan.md --json
{
  "url": "https://opendocs.cc/acme/auth-migration-plan",
  "slug": "auth-migration-plan"
}

# Agent's final response to the user:
# "Plan published: https://opendocs.cc/acme/auth-migration-plan"

The user gets a URL, not a filename. Click, read, done. No more "where did the agent save that file again?"

What agents publish

• PRDs. Let the agent draft the product requirement, publish to a workspace link product can comment on.

• Code reviews. Agents are good at first-pass review. Publish the writeup so the author can read it without opening their IDE.

• Specs and ADRs. Keep them in the repo for version control, publish them to a URL the rest of the org can read.

• Audits. Security review, dependency audit, performance baseline. The agent runs the audit and the URL goes to the security channel.

• Migration plans. The agent surveys the codebase, drafts the plan, publishes it. Reviewers comment via the URL instead of cloning the branch.

Setup is one install

# Install once
npm install -g @opendocs.cc/cli

# Authenticate (one-time, opens browser)
opendocs login --browser

# Publish, get a shareable URL back
opendocs publish report.md --json

Want to teach the agent the workflow? Point it at our SKILL.md. It's a Markdown file that documents the OpenDocs CLI in a shape agents can read.

Per-agent guides