Command Content

/dr-write

Create written content with structured writing workflow

Overview

/dr-write handles content creation: articles, blog posts, documentation, research papers, social media posts, or any structured text. The Writer agent follows a defined pipeline — research, outline, draft, self-review — and deliberately avoids common AI writing patterns from the start.

Usage

/dr-write "API documentation for the payments module"
/dr-write path/to/existing-draft.md
/dr-write "LinkedIn post about our new feature"

What It Does

  1. Understand the Request — determines content type (article, docs, research, social media, report), target audience, register (formal, conversational, academic), length, and platform.
  2. Research and Plan — gathers sources, creates an outline, identifies claims that will need verification later.
  3. Draft — writes from the outline, one section at a time. Applies the humanize skill from the start to avoid AI patterns in the first draft.
  4. Self-Review — checks structure, flow, factual claims, and naturalness. Flags sections that need fact-checking or style review.
  5. Output — delivers the draft with editorial notes marking areas for review.

Arguments

A topic description or a file path to an existing draft to continue working on.

Output

Draft content with editorial notes. Does not write to datarim/ files unless the task is part of the pipeline.

Content Types

  • Articles and blog posts
  • Technical documentation
  • Research papers
  • Social media posts (multiple platforms and languages)
  • Reports and legal documents

Example Session

> /dr-write "Technical blog post about our migration to PostgreSQL"

Audience: developers, technical readers
Register: conversational technical
Length: ~1500 words

Creating outline:
  1. Why we migrated (pain points with MySQL)
  2. Evaluation criteria
  3. Migration approach (dual-write period)
  4. What went wrong (and how we fixed it)
  5. Results and metrics

Drafting...

Draft complete (1,420 words).
Flagged for review:
  - Section 3: verify migration timeline accuracy
  - Section 5: confirm latency improvement numbers

Next steps:
  /dr-edit for fact-checking and polish
  /factcheck for quick claim verification

Related Commands

  • /dr-edit — editorial review: fact-checking and AI pattern removal
  • /factcheck — quick targeted fact verification
  • /humanize — quick targeted AI pattern removal