Technical Writing (Deep Workflow)

Technical writing succeeds when readers can act or decide with less confusion. Optimize for clarity, correctness, and appropriate depth—not word count.

When to Offer This Workflow

Trigger conditions:

• New feature docs, migration guides, API references
• RFCs, ADRs, architecture summaries
• Runbooks, onboarding docs, postmortems (writing-heavy)
• “Make this clearer” edits on existing pages

Initial offer:

Use six stages: (1) define audience & goal, (2) outline & scope, (3) draft core content, (4) examples & edge cases, (5) review for clarity, (6) ship & maintain. Ask for template or style guide if org has one.