Choose developers by the task they need to complete

Hi,

For an illustrative CLI that checks deployment configuration, the intended reader might be a developer preparing a release in a supported environment. That describes a task to investigate. “Everyone who codes” leaves the situation and requirements unclear.

Write the task, its trigger, the supported runtime and the result the developer needs. Distinguish those requirements from discovery filters such as company size or community membership. Identify who would approve using the tool in the team's workflow.

Use the audience worksheet to record the hypothesis. The marketing data sources directory can provide background sources; broad developer survey data does not establish demand for your particular CLI.

Next, shortlist two routes from the distribution directory. Check their audience and current participation rules before preparing a contribution.

This week, write one task-specific tutorial brief. State who can use it, what they need and how they will recognize success. Use the technical distribution guide to connect that brief to an appropriate contribution.

Jon