Can Packer HCL with multiple builds define dependency/ordering?

I’m curious if Packer HCL’s multiple build blocks have a method of declaring intermediary build steps and ordering?

I’d like to create GCP or AWS machine images where I have a root archetype and different trees of image hierarchy. Can this be achieved dynamically with a single packer execution and not having to manually update image names to reference previously built artifacts?

The goal would be a single packer run. If it needs to be multiple executions to handle the ordering, then is it possible to have a subsequent run read from the previous build’s manifest json? I’m trying to figure out how much of this is possible with packer and to not build up scripting around something the tool can already achieve.