A prompt that makes the next step clear
Good prompts contain four things: the target, the outcome, the constraints and the evidence you expect back. You do not need to know internal IDs. Use recognizable names, then let Work discover authorized records and ask you to choose when the match is ambiguous.
“Optimize everything” leaves too many decisions unstated. “Audit the selected Google Ads account for the previous calendar month; compare campaigns, preserve the attribution definitions, and do not change budgets” gives the assistant a useful boundary.
Say whether this is analysis or implementation
Analyze this Close Forge deployment. Explain its message sequence and identify improvements. Do not apply changes, publish a workflow or activate the deployment.
Analysis should return findings and recommendations. A later instruction to implement a specific recommendation starts a different path: prepare a scoped change and request approval. Additional general advice is not automatically an executable recommendation.
Use the current page carefully
The open page can help identify a Site Spark form or Close Forge deployment, but navigation is not permission to change it. Read the target on every proposal. A saved recommendation belongs to the original deployment and version—even if you move to another app while discussing it.
When following up, name the deployment and the recommendation you mean. If it has changed, ask for a fresh analysis. Do not ask Work to force an old preview onto a newer record.
Include dates and measurement definitions
Compare Google Ads spend and platform-reported conversions for September 1–30, 2026, for the account named Main Service Area. Report the currency, date coverage and any partial results. Keep TradeVulcan booked jobs separate unless you can verify the mapping.
Use actual completed dates relevant to your question; the dates above are an example. A rolling “last 30 days” report and a calendar-month report are not interchangeable. Neither are platform conversions, qualified leads, bookings, completed jobs and collected revenue. Ask Work to explain missing coverage instead of filling gaps with assumptions.
Protect what should stay unchanged
Shorten the first step description on the selected unpublished form to one sentence. Keep the step order, fields, required flags, consent text and CRM mapping unchanged. Show me the wording before saving.
For a website edit, identify the page and section, state the approved offer and ask for a preview branch or deployment first. For a message, give the channel, exact recipient and approved content. For a file, state the format and purpose.
Split broad projects at decision points
Begin with discovery, then selection, then a bounded draft. Review factual assumptions before asking for external changes. A plan can coordinate supported dependencies, but it cannot grant itself permission to spend money, publish content, contact people or delete records.
A useful final instruction is: “Tell me what you changed, what you did not change, which result you verified, and where I can inspect it.” That makes the conversation easier to audit and continue later.