Turning an Ad Hoc Workflow Run Into a Repeatable Command

An engineer types ultracode: audit every route handler under src/routes/ for missing auth checks and gets back a fan-out run with one subagent per file, followed by a ranked report. It's exactly what the team wants to run before every release, so the engineer wants to make it repeatable for the whole team without re-typing the prompt or re-explaining the orchestration each time.

1. Should this become a skill or a saved workflow? Justify the choice based on what actually happens when it's invoked.
2. Concretely, how does the engineer save it, and where should it live so every teammate who clones the repo gets it automatically?
3. Two months later, the platform team wants to ship this same audit (plus three other pre-release checks) to six other repos as one package. What changes about how it's invoked once that happens?