How to use this in Confluence

1. Copy/paste this page into Confluence.
2. Replace Markdown checklists (- [ ]) with Confluence checkboxes.
3. Use Confluence panels (/info, /note, /success) to recreate the guidance boxes.
4. Save as your working PRD inside a Jira-linked Confluence page.

👉 Readme.io is the source of truth. Always copy from here to ensure you’re using the latest version.

---

PRD Template: Agentic Experience

Owner(s): Date: Target Release: Rollout: (alpha %, beta %, GA %) Status: Draft / Review / Final

---

1. Outcomes

What is the user outcome we want to drive? What should the agent do end-to-end?

• Provide a one-prompt flow that simplifies a complex workflow.
• Identify gaps or missing info and propose next-best actions.
• Execute approved updates directly in the product.
• Generate a summary or artifact (e.g., report, plan, or notes).

Example From a simple chat prompt (“Create a task to follow up with ACME”), the agent:

• Surfaces missing info (due date, owner)
• Proposes next steps
• Writes back a new Task record in the system
• Generates a short summary of “what changed”

---

2. User Role

Who is this for?

Primary:

• End User (e.g., Sales Rep, Customer Success Manager)

---

3. Scenario Description

3.1. Current Flow (without AI)

• List the steps a user takes today

Example Navigate to Task module → enter details → save

3.2. AI-Enabled Flow (with Agent)

• Describe how the agent automates and simplifies

Example User: “Create a task to follow up with ACME tomorrow”

• Agent detects missing info
• Agent opens Chatterblock to confirm
• On approval, writes back + generates recap

---

4. AI Interaction Modes

Which modes does this experience use? Check all that apply.

• Text (chat)
• Voice (hands-free)
• Navigation (agent moves app view)
• Chatterblock (embedded UI approval)
• Interactive (agent updates screen directly)
• Canvas (workspace for notes, briefs, drafts)

---

5. Suggested UX Design(s)

What should the user see/hear?

• Conversational tone: propose → confirm → execute
• Show proposed changes in Chatterblock with Approve/Reject
• Navigate to updated record after confirmation

Attachments:

• Wireframes / mockups
• Demo video (optional)

Tip Keep the flow lightweight: show → confirm → execute. Don’t overwhelm the user with too many branches.

---

6. Success Metrics

How do we measure user success/adoption?

---

7. Business KPIs

How does this tie to business outcomes?