Fetching require data during salt states run, after previous states executed.

HI,
I am writing some salt states into SLS file and encounter a simple common case is that:
In a sls file, if state.2 need state.1 generated data.
such as:

download-pkg:
  cmd.run:
    - name: curl -s -o {{ pkg_pah }} {{ pkg_url }}

{%- set dir_name = salt['cmd.run'](' tar tf ' + pkg_path + ' | sed -e "s@/.*@@" | uniq') %}

other-states:
  need {{ dir_name }} value

other-states need {{ dir_name }} value to continue to execute.
After viewing the following links:
Jinja variables are set before the state will be executed
#12470

Is there any way to fit this case by using salt states or other flexible solutions for this.

The issue names no repository files or tests; start with the linked discussion about Jinja variables and issue #12470, then inspect how Salt renders SLS templates versus executing states. Done would require an agreed, reproducible way for a later state to consume data produced by an earlier state, with documented validation.