write-opinion

Write Opinion Piece

You are helping write an opinion piece for the author.

Before Writing

1. Run ./scripts/print-published.sh opinion to read all published opinions in one call
2. Note topics, arguments, and examples already used
3. Pay attention to recent patterns to avoid repetitive structures, openings, or phrases
4. Read guidelines/opinion.md for style rules (includes language and publication targets)
5. Read references/professional-profile.md for background

Avoid Repetitive Patterns

When reading recent pieces, actively note and vary:

Openings: If recent pieces start with scene-setting in a specific location, try a different concrete opening (an action, a quote, a surprising fact) Sentence rhythm: Vary between punchy short sentences and longer flowing ones Closing formulas: Don't repeat the same forward-looking structure - find fresh ways to land the argument Examples: Rotate between local and international examples; between industry, government, and everyday life Rhetorical devices: If recent pieces use lists or parallel structure heavily, try a different approach

The goal is a consistent voice with varied execution. Each piece should feel fresh while still sounding like the author.

Style Requirements

• Target ~3500 characters (use wc -m to verify)
• Write in the language specified in guidelines/opinion.md
• Open with concrete scene-setting (time, place, action)
• Strong, vivid verbs
• Short punchy paragraphs (2-4 sentences)
• Double dashes (--) for emphasis
• Forward-looking, grounded close

Process

1. Develop the angle and core argument
2. Write in the language specified in the style guide
3. Check character count against ~3500 target with wc -m
4. Save to content/posts/ with type: opinion, stage: 02-drafts

Validation

After saving the draft, run the character count checker:

scripts/check-char-count.sh <yaml-file>

Adjust the content if the character count is outside the 3000-4000 range.

Sub-Agent Review

Before presenting the final draft, spawn a sub-agent to review with fresh eyes. The reviewer should:

• Check voice consistency against guidelines/opinion.md
• Verify the opening is concrete (time, place, action) not abstract
• Flag any overlap with published opinion pieces
• Check for weak verbs, overly long paragraphs, or generic phrasing

Incorporate the reviewer's feedback before finalizing.

Creating New Files

Get timestamp first:

date -u +"%Y%m%d-%H%M%S"  # For slug
date -u +"%Y-%m-%dT%H:%M:%S.000Z"  # For created/lastUpdated