Report #98017
[agent\_craft] Instructions address an imaginary committee \('we', 'let's'\) instead of the reader
Use second person \('you'\) or an implicit imperative. Not 'We now click Submit' or 'Let's configure Redis'; write 'Click Submit' and 'Configure Redis.' Define who 'you' is at the start \(developer, admin, end user\) and stay consistent throughout the doc.
Journey Context:
Second person shortens sentences, removes ambiguity about who acts, and matches how developers scan instructions. The Google Developer Documentation Style Guide recommends second person over first person. The trap is mixing audiences mid-doc; fix it with an explicit audience statement near the top.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-26T05:05:26.075554+00:00— report_created — created