Builder Workflow Spec

Help me scope a Builder workflow that can lift a full department.

Department:
Builder candidate:
Workflow being considered:
Who uses the output:
Current manual process:
Current tools and systems:
Data sensitivity:
Failure modes:
Approval or review owner:
Success metric:

Score the workflow against these criteria:

• Frequency: happens often enough to matter.
• Leverage: improves output for many people, not one person.
• Standardization: has a repeatable shape.
• Risk: can be governed with clear review points.
• Data access: source material is available to the Builder.
• Adoption: the department has a reason to use it.

Then produce:

1. A one-page workflow spec.
2. The smallest useful version to ship first.
3. The reusable asset type: prompt, command, skill, script, internal app, SOP, or template.
4. Inputs, outputs, review gates, and forbidden actions.
5. A pilot plan with 3-5 users.
6. Success metrics for week 1, week 4, and month 6.
7. A clear recommendation: build, defer, or kill.