Workflows can behave exactly like software templates plus much more features and advantages when using them. However unlike software templates there's no way to edit software temples or creates workflows from within backstage.
If we want to help debug or have users develop and iteract with a workflow code, we can at minimum show them the workflow repository, let them clone and reproduce a behaviour with local tools and so on.
If we represent the deployed workflows as software componenet in the system , then we can directly point at the code, the docs, diagram, Jira tickets and possibly even workflows runs of a specific workflow software component.
If a workflow misbahaves, and looking at the execution reply is not enough, then we can link it the page of a workflow from the orchestrator page into the software component , and from there link with far more information like mentioned above, all the way the git repo, and users can clone the repo with one click , and start the process of development/debug.

We can automatically add a software component of a workflow we detect by the entity provider (currently disabled) .
We can also supply catalog yaml with the workflow repository code and register that location.