developer-docs-audience-research

• SKILL.mdcore · 3,649 bytes
• guidelines.mddoc · 1,707 bytes
• references/core/knowledge.mddoc · 8,924 bytes
• workflows/define-learning-objectives.mddoc · 2,391 bytes
• workflows/map-doc-audience.mddoc · 2,359 bytes

# Developer Docs Audience Research

Use this skill to understand who developer documentation is for before planning, writing, or reorganizing docs. It helps agents turn vague audiences into concrete users, goals, questions, journeys, and validation work.

This skill is derived from Jared Bhatti, Zachary Sarah Corleissen, Jen Lambourne, David Nunez, and Heidi Waterhouse's *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 1, "Understanding your audience." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 3, "Audience," Chapter 9, "Learning Objectives," and Chapter 25, "Writing SaaS Documentation." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6

## Quick Start

1. Load `guidelines.md` to choose the smallest useful reference set.
2. Start from the user's doc artifact or product surface, not from a generic audience label.
3. Identify user goals, learning objectives, business goals, user traits, questions, and missing knowledge.
4. Use `workflows/map-doc-audience.md` when the user needs a full audience brief.
5. Mark assumptions and recommend validation through user conversations, support data, analytics, or a friction log.