Converting a Folder of Subagent Prompts into a Saved, Distributed Workflow

Your team has an informal review process: whenever someone opens a PR, whoever's reviewing it manually copy-pastes five different prompts (stored as plain text files in a shared review-prompts/ folder) into Claude Code one at a time — one for security, one for performance, one for test coverage, one for style consistency, and one that reads the first four agents' output and writes a combined summary. It works, but it's manual, inconsistent (people skip prompts when in a hurry), and only exists on the original author's machine.

1. Explain how you'd ask Claude to turn this into a dynamic workflow, and what phase structure the resulting script would likely have — specifically, which of the five steps can run in parallel and which one is a genuine barrier.
2. Once you have a working run, explain the exact save mechanics you'd use to make it a shared team command rather than something only you can run, including which of the two save locations is correct here and why.
3. Your team wants this same review workflow available in two other repositories your team owns, not just this one. Explain the distribution mechanism this subject covers that fits that requirement, and what the command would be called once distributed.