Another approach for supporting prefetching would be something like useUtils from trpc (which I'd prefer).
I assume you're prefetching in solid router's load functions? This approach would allow you to do something like this (assuming the router is wrapped with rspc's provider)

function load() {
  rspc.useUtils().prefetchQuery(["some.key"])
}

And your example could be

const rspcUtils = rspc.useUtils();
rspcUtils
  .fetchQuery(["your-query-key", { param: test }])
  .then((result) =>
    rspcUtils.prefetchQuery(["your-query-key-2", { param: request1Result }]),
  );

The utils object would basically be a typesafe wrapper around all of the QueryClient's functions. Whether you consume them inside a createResource or an event handler or a load function would be up to you.

I see... That was also the direction @oscartbeaumont was pointing in I think. Totally didn't get it the first time around.

Will have a look at the implementation from trpc.

Made another attempt looks more like this now:

const queryUtils = directory.createQueryUtils();

queryUtils
  .fetchQuery(["orgs.list"])
  .then(orgs => {
	  const currentOrgId = orgs?.find(org => org.slug === params.orgSlug)?.id;
	  if (!currentOrgId) throw new Error("Could not find org");
	  console.log("prefetch org");
	  return queryUtils.prefetchQuery(["invitations.listByOrg", currentOrgId]);
  });

Updated the naming of the export to useUtils and updated the description.