Technical Writing

Router skill for comprehensive technical writing. Dispatches to handler files based on content type. Always: clear structure, audience-appropriate, no fluff.

When to Use

• Writing or updating documentation (README, API docs, guides).
• Generating changelogs from conventional commits.
• Creating pitch decks, sprint reviews, blog posts, architecture board presentations.
• NOT for code explanations -- use /ai-explain.
• NOT for code changes -- use ai-build agent.

Routing

Default (no sub-command): docs.

Audience Targeting

Default: developer.

Quick Reference

/ai-write docs                              # documentation (default)
/ai-write changelog                         # release notes from commits
/ai-write content pitch                     # elevator pitch
/ai-write content sprint-review             # sprint review summary
/ai-write content blog                      # blog post
/ai-write content presentation              # presentation outline
/ai-write content architecture-board        # architecture decision for review
/ai-write content solution-intent           # solution intent document
/ai-write docs --audience manager           # manager-targeted docs

Shared Rules

• Write what users can DO, not what you BUILT.
• Active voice. Present tense.
• No "basically", "simply", "just".
• Every section earns its place -- cut anything that does not serve the reader.
• Audience determines vocabulary, not quality.

Integration

• Composes with /ai-commit documentation gate for auto-updates.
• Changelog mode follows Keep a Changelog format.
• Content mode adapts to audience tier.

References

• .ai-engineering/manifest.yml -- governance documentation requirements. $ARGUMENTS