What I do for projects in early stages and personal goals is the following.

1. Take a big piece of paper (A2/A3)

2. Write the goal on the right-hand side of the paper

3. Try to visualize what the goal looks like

4. Then I try to visualize the step right before the goal would look like

5. Write that down and draw a line to the parent goal

6. Move leftward and repeat

In my experience, the further you move to the left side of the paper, the more concrete and actionable the goals are. This will lead to a lot of sub goals and tasks that can be prioritized, revisited and continuously refined. Within the context of software projects, I find it important to work on the definition of done for the goals. I redraw the breakdown many times during the early stages of projects, until it can be put into a project management tool or similar. For personal stuff, I always just stick to the paper method and keep the latest iteration.

It is harder with more abstract goals (become an tech lead for my team; become a trusted advisor for management; be able to read and comprehend new ML research on arXiv etc.). If you are in software, breaking down semi-large projects is a good exercise. For other areas, I recommend starting with a goal that is abstract, but also attainable within months.

2. PMP Cert also talks of Work BreakDown charts but thats too official.

Its more like finding your own routine/pace which allows for some serendipity and pays your bills and keeps you interesting

Every time I start with forks and spoons, then I wash cups, next plates and the big pans and pots last.

Every time I get to do anything I try to get small wins and increase difficulty over time.

Just ask what is the easiest task that can be done, and when you finish, next easiest task will be more difficult because you selecting tasks from a finite list of tasks.