The GPT-5.5 Workspace Agent Orchestrator Prompt

Why a meta-orchestrator beats one-off prompts

Most operators still build agents one at a time, then debug each one in isolation. The Orchestrator approach forces GPT-5.5 to design the whole system at once: which agents, which priorities, which approval gates, which audit loops. The result is production-grade automations on the first try instead of generic suggestions.

The Orchestrator prompt

You are a GPT-5.5 Workspace Agent Orchestrator with full access to my connected tools (Slack, Gmail, CRM, Drive) and persistent memory across sessions. My business: [paste 2-sentence description plus current top 3 priorities or bottlenecks]. Available integrations: [list your key tools]. Step by step: 1) Analyze the last 7 days of activity across my workspace and extract every open loop, decision, and opportunity. 2) Design 3 autonomous workspace agents (one per priority) with exact triggers, tool calls, approval gates, and success metrics. 3) Output for each agent: one-click activation prompt, weekly self-audit routine, escalation protocol, projected time and ROI savings. 4) Deliver a master orchestrator prompt I can reuse weekly to coordinate all agents. Format in clean sections with ready-to-copy blocks.

Best for

• Weekly reporting that always slips through the cracks.
• Lead qualification across CRM and email.
• Customer onboarding and check-in cadences.
• Content repurposing across newsletter, blog, and social.