Academy
6. Handle Big Tasks: Split or Delegate
Recognize when a task is too large for a single prompt and learn to break it into steps or hand it to Conductor.
Not every task fits in a single prompt. When you ask a model to research a topic, draft a full report, format it, and add citations — all at once — you overload the request. The model tries to do everything simultaneously, and quality drops on every front. The rule of thumb: if your task has distinct phases (plan, then produce, then refine) or needs different tools along the way, it is too big for one shot. Recognizing this is the first skill; the second is knowing what to do about it.
The simplest fix is to split the work yourself. Ask for a plan or outline first. Read it, adjust it, then ask the model to execute one section at a time. Each prompt stays focused on a single, clear goal — which is exactly what makes prompts succeed. You keep control at every stage: you validate the structure before any content is written, and you can give targeted feedback on each part without losing what already works. This is iterating in place, and it beats starting over every time.
When you split a task, put the essential instruction first in each prompt, the material after, and the desired format at the end. Relevant context helps; irrelevant context dilutes attention. Each sub-prompt should be as long as it needs to be — and not one line more.
Some tasks are not just big — they are complex. They need multiple steps, different tools (web search, document analysis, code execution), and decisions along the way. That is not a prompt; that is a mission. Hand it to Conductor. Conductor plans the work, executes step by step, picks the right tools, and reports back. You describe the end goal and the constraints; Conductor handles the orchestration. Think of it as delegating to a capable assistant instead of micromanaging every move.
How to choose: if you can list 2–3 clear steps and want to review each one, split the task yourself in ChatPro. If the job needs tools, has many steps, or you want hands-off execution, delegate to Conductor via the Assistant.
Open the Assistant (dashboard.user.assistant). Give Conductor a multi-step task — for example: "Research three competitors in [your industry], summarize their positioning in a table, then draft a one-page differentiation memo." Watch how it plans and executes each step. Review the output and refine with targeted feedback.
Once you find a splitting pattern or a Conductor mission that works well, do not let it stay in your chat history. Turn it into a reusable skill or agent in OUPI. A skill stores the instruction so it is applied automatically — no copy-pasting. Good prompts are assets: name them, version them, share them with your team. What started as a workaround for a big task becomes a reliable, repeatable workflow.
When a task is too big for one prompt, you have two moves: split it yourself (ask for a plan, validate, then execute part by part) or delegate to Conductor for multi-step, multi-tool missions. Keep each sub-prompt focused with a clear goal, relevant context, and an explicit format. Iterate in the same conversation with targeted feedback. When a pattern works, save it as a skill or agent so your team can reuse it.