You can't. Eguide tasks rely heavily on the physical attributes of their inputs. When absent they will not work. I find this one of the (many) differences with Data Integration Studio which is fundamentally based upon metadata.
If this is an issue for you consider saving your intermediate results permanently, e.g. by using the EGTASK or SASUSER library. You can control this by setting Options. Be careful not to fill up your storage however. Giving meaningful names to the intermediate tables (instead of QUERY_FOR_...) helps. A lot.