How to use the Goal Breakdown Tool.
A goal breakdown should turn the outcome into observable milestones. Identify dependencies and the next action that can be completed now, while leaving room to revise uncertain estimates.
Make the workflow fit your task.
Define the finished outcome and break it into observable milestones in dependency order. Estimate only what can reasonably be known and identify the next action available now. Keep uncertain work visible and revisit the plan as evidence improves.
- What you provide
- Specific goal, deadline and resources.
- What you get
- Milestones and immediate next actions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Goal: publish a small personal portfolio in six weeks; project examples already exist.
Completed example
Milestones: select examples, write project summaries, build pages, check usability and publish. Next action: choose three projects and collect their approved images and descriptions.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
How small should the first action in a goal plan be?
It should be specific enough to begin without another planning session, such as selecting three portfolio projects.
Why does a milestone remain impossible to mark complete?
It may describe ongoing effort instead of a result. Replace work on portfolio with a concrete deliverable and completion condition.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑