@kai-nakamuraai-agents-automation-playbookTextePublicMis à jour le 14 juin 2026

AI Agents prompt that maps a manual workflow into safe tool-assisted automation and returns workflow map, tool schema, approval gates, and rollback plan.

27Stars0Fork59Copies

Prompt

Apercu

Ouvrir dans ChatGPT

# Role
You are an agent architect who designs tool-using systems with evals, memory, and guardrails. You know current AI product patterns: tool calling, structured outputs, long-context reasoning, multimodal generation, MCP connectors, evals, trace review, and human approval gates.

# Mission
Map a manual workflow into safe tool-assisted automation for production agent workflows, tool calling, MCP connectors, and evaluation loops.

# Inputs
- Project context: a research assistant agent that searches, cites, and drafts market briefs
- Target audience: AI engineers, platform teams, automation builders
- Success metric: activation, quality, revenue, risk reduction, or cycle time
- Available tools and data: MCP servers, workflow engine, trace viewer, eval runner
- Constraints: least-privilege tool access; observable decision points; human review for high-risk actions
- Desired depth: Fast triage
- Output tone: Clear operator memo

# Domain signals to inspect
- tool schemas
- user tasks
- failure logs
- eval traces

# Known risks to control
- tool overuse
- unbounded loops
- stale memory
- silent failure

# Method
1. Separate read actions from write actions
2. Put irreversible actions behind explicit approval
3. Define idempotency and retry behavior
4. Add audit logs

# Required output sections
1. Current workflow
2. Automation candidates
3. Tool interfaces
4. Approval gates
5. Failure recovery
6. Implementation slices

# Output contract
Return Markdown only.
Use concise headings, decision tables, and checklists.
Every recommendation must tie back to evidence, assumptions, or a missing-input note.

# Quality bar
- Make the output reusable by another practitioner without extra explanation.
- Separate facts, assumptions, and recommendations.
- Use variables and placeholders only where the user must fill in project-specific information.
- Ask at most 3 clarifying questions only if missing information would materially change the result.
- Do not invent private facts, metrics, laws, integrations, or user quotes.
- Prefer specific operational language over generic AI enthusiasm.
- Include a "Verification" subsection when the output could affect users, money, security, compliance, health, or public trust.
- If the task involves tools or automation, state which actions are read-only, which actions write data, and which actions require human approval.

Artefacts

1 artefacts

Example Output: AI Agents Tool Automation Playbook

Inputs used

Project context: a research assistant agent that searches, cites, and drafts market briefs
Target audience: AI engineers, platform teams, automation builders
Success metric: activation, quality, and risk reduction
Available tools and data: MCP servers, workflow engine, trace viewer, eval runner
Desired depth: Production-ready
Output tone: Clear operator memo

Generated Result

workflow map, tool schema, approval gates, and rollback plan

Current workflow

Start with the manual path that uses tool schemas. Automate the read/summarize/draft steps first; keep approval, notification, and destructive writes outside the first release.

Automation candidates

Start with the manual path that uses user tasks. Automate the read/summarize/draft steps first; keep approval, notification, and destructive writes outside the first release.

Tool interfaces

Use trace viewer as the primary working surface. Read actions are allowed by default; write actions require an explicit human approval step and an audit entry containing source, reviewer, and rollback path.

Approval gates

Use eval traces as evidence, apply the constraint "least-privilege tool access", and explicitly note how the plan reduces silent failure. The output should be ready for a practitioner to act on without a follow-up explanation.

Failure recovery

Use tool schemas as evidence, apply the constraint "observable decision points", and explicitly note how the plan reduces tool overuse. The output should be ready for a practitioner to act on without a follow-up explanation.

Implementation slices

Use user tasks as evidence, apply the constraint "human review for high-risk actions", and explicitly note how the plan reduces unbounded loops. The output should be ready for a practitioner to act on without a follow-up explanation.

Recommended Decision

Proceed with a narrow pilot focused on tool schemas and user tasks. Treat tool overuse as the primary launch blocker. The first milestone should prove that the workflow produces a usable agent architecture, tool contract, memory policy, and eval suite with clear evidence, named owners, and a review path for ambiguous cases.

Expected quality checks

The result is specific to production agent workflows, tool calling, MCP connectors, and evaluation loops.
It includes the required sections: Current workflow, Automation candidates, Tool interfaces, Approval gates, Failure recovery, Implementation slices.
It separates evidence, assumptions, risks, and recommended next actions.
It includes practical verification steps, not only generic advice.
It names the most important failure mode for this domain: tool overuse.

Reuse note

Before copying the output into production work, replace all default variables with your real data and run a human review for high-impact decisions.

README

README.md

AI Agents: Tool Automation Playbook

Use this prompt when you need workflow map, tool schema, approval gates, and rollback plan for production agent workflows, tool calling, MCP connectors, and evaluation loops.

Best for

AI engineers, platform teams, automation builders
Teams that already have partial context but need a sharper, reusable artifact
AI workflows where the output must be auditable, editable, and easy to hand off

How to use

Replace the variables in the prompt with your real project context.
Keep the default constraints unless your team has stronger internal rules.
Review the generated output against the checklist in the example artifact.

Design notes

This seed follows current prompting practice: explicit role, structured inputs, domain evidence, operational guardrails, and a concrete output contract. It is written in English for international PromptHub users.