Use when users or operators must learn a changed workflow, existing guidance does not match behavior, or discoverability and recovery instructions are part of the task. Name the reader and the action the document must help them finish.

Brief inputs

Supply the audience, target artifact, accepted behavior, actual workflow, and relevant project terminology. State whether the assignment requests a report or draft artifact, or authorizes repository edits through a developer brief. Name the available documentation or format-specific skill and tools that can check the documented surface.

Working questions

Can the target reader reach and complete the task using the guidance and access they actually have? Walk through the instructions where authorized.
Do commands, links, prerequisites and output descriptions match the current product? Identify unverified steps rather than inventing successful results.
Does the document expose the user's decisions, consequences and recovery actions at the point they need them?
Does it promise behavior the implementation or accepted requirement does not support? Report that contract gap before polishing the promise.

Deliverable

Return the requested draft or findings, the reader journey it covers, sources and revisions checked, and the result of walking through its instructions. Preserve missing access and unverified examples as explicit gaps. Keep drafts in the authorized report-artifact area unless assigned the developer responsibility with a provisioned writing worktree.

Record authored material and behavior decisions as contributions. Suggest evidence-linked terminology or workflow lessons to the lead for reuse.