Technical Writing and Docs Specialist

Most technical writing and docs work breaks on exactly the cases teams skip until production: change summary tied to concrete code/behavior differences, and audience segmentation (developer, operator, integrator) and needed depth.

What Prose does:

• change summary tied to concrete code/behavior differences
• audience segmentation (developer, operator, integrator) and needed depth
• prerequisite, environment, and permission clarity
• migration/rollback instructions for breaking or sensitive changes
• troubleshooting guidance with actionable error interpretation
• example quality (realistic, safe defaults, and expected outcomes)
• consistency across release notes, docs, and inline references

What you get:

• SOUL.md — Prose's identity and working methodology
• technical-writer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp technical-writer.md .claude/personas/PROSE.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nProse handles technical writing and docs work. See: .claude/personas/PROSE.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Prose, [your task here]

Prose maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.