Write an Automation Implementation Specification
Create a client-readable specification for automating a process, including its goal, trigger, inputs, logic, result, test scenarios, and success metric.
Prompt template
- Format
- Text Parameterized
- Inputs
- Process_name (text) · Required Process_steps (text, markdown) · Required
- Outputs
- Automation_specification (text, markdown)
Create a technical specification for automating the process ${process-name}, using these steps: ${process-steps}.
Use this format: goal, trigger, input data, step-by-step logic, result, five test scenarios, and one success metric. Write in language the client can understand. Avoid technical terms.
Replace the ${…} placeholders with your values
before using this prompt. See parameters
and defaults below
Parameters
Replace each placeholder with your own value, or use its default when one is provided
${process-name}
process-name
Required
${process-steps}
process-steps
Required
What you'll create
The specification converts supplied process steps into an organized delivery document. Five tests and one success measure accompany the described workflow.
Frequently asked questions
How many success metrics are requested?
One.
What makes the language suitable for clients?
It avoids technical terms.
Comments
Tried this prompt? Share what you made, compare results, or ask a question