Automation Implementation Specification

Create a client-friendly specification for automating a process, with test scenarios and a success metric.

Anton Tsevmenko | AI & Web Developer | Team Lead Republished on Nov 02 0 Bookmarks 0 Copies
Bookmark 0

Prompt template

Format
Text Parameterized
Inputs
process_name (text) · Required steps (text) · Required
Outputs
Automation_specification (document, text)
Create a technical specification for automating the ${process-name} process using these steps:
${steps}

Include:
- Goal
- Trigger
- Input data
- Step-by-step logic
- Result
- 5 test scenarios
- One success metric

Use 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
${steps} steps Required

What you'll create

The document maps a process from goal and trigger through inputs, logic and result. Five scenarios explain expected behavior without specialist jargon.

Frequently asked questions

How many test scenarios are requested?

Five.

Should technical terms dominate?

No. The language stays understandable to the client.

Comments

Tried this prompt? Share what you made, compare results, or ask a question

Up to 4 results. Images up to 2 MB; MP4, WebM, or MOV videos up to 4 MB each