Command Content

/dr-publish

Prepare platform-adapted publish payloads for approved content (does not send them)

Overview

/dr-publish is the final step in the content pipeline. After writing (/dr-write) and editorial review (/dr-edit), this command formats approved content for each target platform, runs pre-publish checks, and prepares ready-to-publish payloads. It does not send anything: public sending is a hard-gated action that happens only through the project’s publishing tool with operator approval.

Usage

/dr-publish path/to/approved-article.md
/dr-publish "Social Media/post.md"

What It Does

  1. Confirm Readiness — checks if the content has been through /dr-edit. Warns if not.
  2. Determine Targets — asks which platforms: Telegram, LinkedIn, Facebook, X/Twitter, VK, Instagram, website/blog, or "all".
  3. Adapt Per Platform — trims text to platform limits, converts formatting (HTML for Telegram, plain text for LinkedIn), prepares images in optimal dimensions.
  4. Pre-Publish Checklist — verifies: text within limits, formatting renders correctly, links valid, images sized, OG tags present (for websites).
  5. Prepare Payloads — for Telegram: ready sendMessage/sendPhoto payloads (the API is not called). For social networks: formatted text plus the publishing-tool invocation, never a direct post. For websites: the content change committed on a feature branch; the site goes live only via a merge to main and CI/CD. When several platforms are targeted, a fixed publishing order applies.
  6. Post-Publish — suggests link preview verification via platform debuggers and back-links the article to its social posts once they exist.

Content Pipeline

/dr-write  →  /dr-edit  ⇄  /dr-write  →  /dr-publish  →  /dr-archive
 (author)     (editor)     (rework)      (publish)       (close)

Related Commands

  • /dr-write — create content (writing phase)
  • /dr-edit — editorial review (fact-checking, AI pattern removal)
  • /dr-archive — close and archive the task

Reporting the result

Apply Human Outcome Reporting before a human-facing update or result. Explain the user-visible outcome, the original conditions, checks and evidence, and open limitations. A stage result does not mean the entire task is complete. Keep exact protocols and technical records intact. To explain again without continuing work, use /dr-explain.