AGENTIC WORKFLOW SPEC — ONE-PAGE TEMPLATE 1) Workflow name - Short name: - Owner (PM/Eng/Design/Sec): - Target user role (e.g., Support lead, SRE, Sales ops): 2) “Done” state in a system of record - System of record (e.g., Jira, Salesforce, ServiceNow, GitHub): - Definition of done (must be verifiable): - Example: “Ticket transitioned to Done, duplicate linked, comment added, required fields valid.” 3) Allowed actions (tool calls) List explicit actions the agent may execute. No freeform “do anything.” - Tool/action: - Required parameters: - Side effects: - Data touched: 4) Permission model - Identity source (e.g., Okta, Microsoft Entra ID, Google Workspace): - Execution identity: - ( ) Agent acts as user - ( ) Agent acts as service account with scoped permissions - Least-privilege scope: - Actions requiring human approval: - Money movement: - Customer communications: - Production changes: - Data deletion: 5) Plan → Preview → Apply UX - Plan output (what the agent must show before any write): - Preview format (diff/checklist/record change list): - Apply controls: - ( ) Single-click approve - ( ) Two-person approval - ( ) Time delay / scheduled execution 6) Audit & provenance requirements - Minimum audit log fields: - timestamp, user, agent version, tool called, parameters (redact secrets), result - Provenance: - List sources shown to user (record IDs, doc links) - What’s explicitly NOT consulted 7) Rollback / remediation - Common failure modes: - Undo strategy per action (revert, reopen, compensate): - Support playbook link: 8) Safety tests (pre-release) Run these as scripted checks: - Low-permission user attempts restricted action: - Agent attempts action without preview: - Agent produces tool call with missing/invalid parameters: - Logging verification (can you trace “why”): - Rollback drill: 9) Launch boundary - What this workflow will NOT do (hard exclusions): - Rate limits / throttles: - Kill switch owner and procedure: 10) Success criteria - Observable outcome in system of record: - Quality bar (validation rules passed, no manual cleanup required): - Operational readiness (audit logs reviewable, approvals enforced):