This guide gives you a reusable starting pattern. It is designed to help you see the work more clearly; it is not a substitute for judgment, source checking, or responsibility for the result.
Prepare the inputs before you ask for output.
The model only sees what you give it. Spend a few minutes naming the reader, desired result, and uncertain information. This makes a first draft easier to assess and reduces the need for decorative rewriting later.
Give the task a useful brief.
Help me make a 30-minute starting plan for this project. Outcome I want: [outcome] What I know: [facts] Constraints: [time, people, tools, risks] What feels unclear: [uncertainties] Give me: a five-minute setup, one focused first task, a checkpoint question, and a stop condition. List risks or decisions that need a human owner. Do not create tasks that depend on facts I have not supplied.
Replace every bracketed field with your real context. Read the output before reuse.
Four steps that keep the result usable.
- 1
Describe the outcome, not just the subject.
- 2
Write down what is unclear.
- 3
Ask for a stop condition.
- 4
Assign risky decisions to a human owner.
Plans should earn their length
When a project feels messy, detailed planning can feel like progress. A better first move is small enough to execute today, with a question that tells you whether the next step is worth taking.
Give uncertainty a place to go
A model can suggest routes, but it cannot decide which trade-offs your team should accept. Asking it to list assumptions, risks, and owner decisions keeps useful structure while showing where judgment belongs.
A worked example: starting a docs project
Suppose the project is “publish setup guides for three integrations”. The uncertainty is which integrations readers actually need. A 30-minute plan might be: five minutes to list the integrations and who asked for them, one focused task to check analytics or tickets for demand, a checkpoint question — “is integration A worth the effort?” — and a stop condition if the evidence is thin. That is a plan you can start today.
Beware the plan that plans forever
When a project feels messy, it is tempting to ask for a detailed plan. If the output keeps adding phases, owners, and dependencies you have not confirmed, cut it back. A starting plan should reduce uncertainty, not create a document that pretends the unknown is settled.
Run a human check.
- Can the first task be started in the time available?
- Is there a clear question that determines the next step?
- Are decisions and risks assigned to a human owner?
- Does the plan avoid pretending unknown facts are settled?
AI is strongest here when it makes missing information, structure, and options easier to see. The moment an output becomes a claim, commitment, or decision, bring a person back into the loop.