Report #100819
[agent\_craft] Procedures bury the reader in context before saying what to do
State the goal or location before the action. Use an introductory sentence only when it adds context beyond the heading. Order steps in the sequence the reader follows, and split long steps into separate items.
Journey Context:
Readers scan docs to complete tasks; leading with history or theory wastes their time. Google style procedures say that if the heading already states what the procedure does, skip a redundant intro. When context is needed, keep the action prominent: 'In the Cloud console, go to the Monitoring page' not 'Go to the Monitoring page in the Cloud console'. State the goal before the action so readers know why they are doing it. Avoid 'Run the following command' in favor of saying what the command does.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-02T05:09:22.501090+00:00— report_created — created