01. Define the finished work
Describe what you need to hand over: a readable document, a research memo, a diagram, or a workflow specification. Include the audience, language, level of detail, and any format constraints.
02. Bring the source material
Use material you are allowed to share. Keep original numbers, units, source dates, and caveats together. Mark gaps explicitly. A clear brief should not require the next agent to invent missing facts.
03. Use the local starting points
The prompt builder creates a structured text template. The workflow composer creates a JSON or Markdown specification. Both work locally, without accounts or model API keys. The exported file is not an executed task.
04. Verify the host before execution
When a public skill release becomes available, use its release-specific installation instructions. Confirm file access, tools, dependencies, and permissions. Do not assume that importing instructions grants an agent the ability to render documents or connect to accounts.
05. Inspect before delivery
Review the result against the source and the request. Check omissions, values, units, language direction, links, and the final rendered layout. Separate content fidelity from factual accuracy. Keep external publishing behind explicit approval.
Bring your next what if.
Start with a brief. Leave with a better way to work.
