CONVERT

Payment

Learn the customer, business, technology, AI, controls, and KPIs for payment.

Learning model: business goal → customer journey → systems/data → failure modes → AI opportunity → human control → KPIs.

Agent patterns

Payment Copilot

Copilot for Payment, using approved data and bounded actions.

Blueprint

Payment Monitor

Monitor for Payment, using approved data and bounded actions.

Blueprint

Payment Recovery Agent

Recovery Agent for Payment, using approved data and bounded actions.

Blueprint

Payment Analyst Agent

Analyst Agent for Payment, using approved data and bounded actions.

Blueprint

Payment QA & Control Agent

QA & Control Agent for Payment, using approved data and bounded actions.

Blueprint

36 prompts

/human

Payment — /human

/human Explain Payment to a fresher using a human story, then a D2C example, workflow, risks, and KPIs.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/visualize

Payment — /visualize

/visualize Visualize Payment as an end-to-end D2C flow with customer actions, systems, decisions, exceptions, and outcomes.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/diagram

Payment — /diagram

/diagram Create an architecture diagram for Payment, showing storefront, services, APIs, data, events, and human approvals.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/flowchart

Payment — /flowchart

/flowchart Create a decision flowchart for Payment, including normal path, exception path, retry, escalation, and safe stop.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/mindmap

Payment — /mindmap

/mindmap Create a mind map for Payment: customer, business, data, technology, AI, risks, KPIs, and owners.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/analysis

Payment — /analysis

/analysis Analyse Payment performance for a fictional D2C electronics business. Segment results, find root causes, quantify impact, and recommend actions.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/RCA

Payment — /RCA

/RCA Create an RCA for a failure in Payment: timeline, symptoms, hypotheses, evidence, root cause, containment, corrective action, prevention, and owner.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/BRD

Payment — /BRD

/BRD Write a detailed BRD for improving Payment: problem, users, scope, process, rules, integrations, errors, analytics, acceptance criteria, and exclusions.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/PRD

Payment — /PRD

/PRD Create a product requirements document for an AI-enabled Payment capability with user needs, UX, logic, APIs, controls, metrics, and rollout.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/userstories

Payment — /userstories

/userstories Write user stories and acceptance criteria for Payment across customer, operations, support, product, and admin personas.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/testcases

Payment — /testcases

/testcases Generate 50 test cases for Payment: happy, negative, boundary, integration, performance, security, accessibility, and business-rule cases.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/UAT

Payment — /UAT

/UAT Create a UAT plan for Payment with scenarios, preconditions, data, steps, expected result, owner, severity, and sign-off.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/API

Payment — /API

/API Design APIs for Payment: endpoints, request/response JSON, validation, idempotency, errors, auth, rate limits, and observability.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/JSON

Payment — /JSON

/JSON Create realistic JSON payload examples for Payment, including success, failure, partial, retry, and exception states.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/SQL

Payment — /SQL

/SQL Write SQL analysis questions and example queries for Payment: funnel, failures, cohorts, anomalies, SLA, and business impact.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/dashboard

Payment — /dashboard

/dashboard Design an executive and operations dashboard for Payment with metric formulas, dimensions, thresholds, alerts, owners, and decisions.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/KPI

Payment — /KPI

/KPI Define a KPI tree for Payment: north-star, leading, lagging, customer, commercial, operational, quality, and risk metrics.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/agent

Payment — /agent

/agent Design an AI agent for Payment: objective, trigger, state, tools, APIs, memory, rules, confidence, approval, audit log, KPIs, and tests.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/multiagent

Payment — /multiagent

/multiagent Design a multi-agent workflow for Payment, separating planner, specialist agents, deterministic services, and human approval.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/automation

Payment — /automation

/automation Map Payment and label every step: deterministic automation, AI assist, agent action, human approval, or human only.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/guardrails

Payment — /guardrails

/guardrails Create AI guardrails for Payment: permissions, PII, policy grounding, confidence, financial thresholds, irreversible actions, audit, and rollback.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/evaluate

Payment — /evaluate

/evaluate Create an evaluation framework for AI in Payment: accuracy, hallucination, precision/recall, latency, cost, safety, and business impact.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/monitor

Payment — /monitor

/monitor Design production monitoring for AI-enabled Payment: technical health, model quality, drift, customer harm, business metrics, and alerts.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/incident

Payment — /incident

/incident Create an incident playbook for Payment: detect, classify, contain, communicate, recover, reconcile, and learn.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/SOP

Payment — /SOP

/SOP Write an operations SOP for Payment with roles, prerequisites, normal process, exception handling, escalation matrix, and daily controls.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/checklist

Payment — /checklist

/checklist Create a launch-readiness checklist for Payment: business, UX, content, data, API, QA, security, analytics, support, and rollback.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/roadmap

Payment — /roadmap

/roadmap Create a 90-day roadmap to improve Payment: baseline, quick wins, experiments, AI opportunities, dependencies, milestones, and KPIs.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/prioritize

Payment — /prioritize

/prioritize Prioritise 15 improvement ideas for Payment using impact, effort, confidence, customer value, risk, and dependency.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/executive

Payment — /executive

/executive Create a one-page executive review for Payment: performance, customer impact, revenue impact, top risks, actions, owners, and decisions.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/interview

Payment — /interview

/interview Create 20 interview questions and model answers about Payment for ecommerce, product, and AI manager roles.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/quiz

Payment — /quiz

/quiz Create a 15-question quiz on Payment: beginner to advanced, with answers and explanations.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/project

Payment — /project

/project Create a portfolio project for Payment using fictional data: problem, dataset, analysis, AI solution, architecture, prompts, evaluation, and presentation.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/promptEvolution

Payment — /promptEvolution

/promptEvolution Improve a weak Payment prompt through beginner, structured, expert, and agent-level versions.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/sales

Payment — /sales

/sales Create five D2C sales scenarios for Payment, including intent, recommendation logic, objection, guardrail, and conversion KPI.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/cs

Payment — /cs

/cs Create five customer-service scenarios for Payment, including customer message, system checks, grounded response, escalation, and KPI.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/ops

Payment — /ops

/ops Create five operations scenarios for Payment, with exception, evidence, decision, owner, SLA, and preventive control.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.