template chaining across protocols - on the roadmap?

[arkanzasfeziii]

been using nuclei workflows for a while and they handle basic template orchestration fine, but i keep hitting a wall when i need output from one step to feed into the next across different protocols.

for example on a web engagement:

• subfinder gives me a list of subdomains
• httpx probes which ones are alive
• then i want to fingerprint the tech stack and only run relevant CVE templates against matching targets

right now i just pipe the output between steps with bash, but it would be way cleaner if the template DSL could handle that natively. like having extractors from step 1 available as variables in step 2, with some basic conditions to branch.

is there a plan for something like this, or should i be using the current workflow system differently? curious if anyone else has found a better pattern for this.