Skip to main content

Use Case: Create a PRD

Step-by-step walkthrough for creating a Product Requirements Document using FAOS agents and workflows.

Overview​

MethodDurationBest For
Workflow (automated)30-60 minComprehensive PRDs, following standards
Agent (interactive)VariableQuick drafts, specific sections

Method 1: Using the PRD Workflow​

The create-prd workflow guides you through a structured PRD creation process.

Step 1: Start the Workflow​

Prompt:

"Run the FAOS create-prd workflow for a mobile expense tracking app targeting small business owners"

Response:

Starting PRD workflow...
Workflow ID: wfrun_abc123
Status: running
Current step: Gathering initial requirements

The workflow will:
1. Define product vision and goals
2. Identify target users and personas
3. Document functional requirements
4. Specify non-functional requirements
5. Create acceptance criteria
6. Define success metrics

Step 2: Provide Additional Context (Optional)​

If the workflow asks for more information:

Prompt:

"Add context to the PRD workflow: Our main competitors are Expensify and SAP Concur. We want to focus on receipt scanning and automatic categorization. Budget is $500K for MVP."

Step 3: Monitor Progress​

Prompt:

"Check status of FAOS workflow wfrun_abc123"

Response:

Workflow: create-prd
Status: running
Progress: 45%
Current step: Defining functional requirements
Estimated time remaining: 25 minutes

Step 4: Get Results​

When complete, the workflow provides:

  • Full PRD document
  • User personas
  • Feature prioritization matrix
  • Success metrics

Prompt:

"Get the output of FAOS workflow wfrun_abc123"

Method 2: Using Agents Interactively​

For more control or quick iterations, work directly with agents.

Start with Research​

Prompt:

"Ask FAOS analyst to research the expense tracking app market, focusing on small business needs and current pain points"

Response: The analyst provides:

  • Market size and trends
  • Competitor analysis
  • Common user pain points
  • Feature gaps in existing solutions

Create the Product Vision​

Prompt:

"Use FAOS PM agent to create a product vision statement for our expense tracking app based on that research. Target: small business owners with 1-50 employees."

Response:

Product Vision: ExpenseTrack Mobile

For small business owners who struggle with manual expense
management, ExpenseTrack Mobile is a mobile-first expense
tracking app that automates receipt capture and categorization.

Unlike Expensify which targets enterprises with complex approval
workflows, our product focuses on simplicity and speed for
businesses without dedicated finance teams.

Define User Personas​

Prompt:

"Have FAOS PM create 3 user personas for this expense tracking app"

Response:

Persona 1: Sarah - The Busy Founder
- Role: CEO/Founder of 15-person startup
- Pain points: No time for manual expense reports,
  loses receipts, needs real-time spending visibility
- Goals: Submit expenses in under 2 minutes

Persona 2: Mike - The Field Sales Rep
- Role: Sales representative, constantly traveling
- Pain points: Multiple currencies, delayed reimbursements
- Goals: Capture expenses immediately after purchase

Persona 3: Lisa - The Office Manager
- Role: Part-time bookkeeper for 3 small businesses
- Pain points: Reconciling expenses across clients
- Goals: Clear categorization, easy export to QuickBooks

Write Functional Requirements​

Prompt:

"Ask FAOS PM to write the functional requirements section, focusing on receipt scanning, auto-categorization, and reporting. Use the MoSCoW prioritization method."

Add Technical Perspective​

Prompt:

"Have FAOS architect review these requirements and add technical constraints and architecture considerations"

Create Acceptance Criteria​

Prompt:

"Use FAOS PM to write acceptance criteria for the top 5 must-have features using Given-When-Then format"

Response:

Feature: Receipt Scanning

AC1: Successful receipt capture
Given the user opens the camera
When they photograph a receipt
Then the app extracts merchant, date, amount, and category
And confidence score is displayed
And extraction completes within 3 seconds

AC2: Manual correction
Given a receipt was scanned with errors
When the user taps on a field
Then they can manually correct the value
And the correction trains the ML model

Conversation Example​

Here's a complete conversation flow:

You: Run the FAOS create-prd workflow for a task management app for
     remote teams. Focus on async communication and time zone awareness.

Claude: Starting the create-prd workflow...

        Workflow ID: wfrun_task_mgmt_001
        Status: running

        I'll guide you through creating a comprehensive PRD.
        The workflow will take approximately 30-45 minutes.

        First question from the workflow:
        Who is the primary target user for this task management app?

You: Software development teams of 5-20 people, distributed across
     multiple time zones (US, Europe, Asia).

Claude: Got it. The workflow is processing...

        Current step: Defining user personas
        Progress: 15%

        Next question: What existing tools are these teams currently
        using, and what are their main frustrations?

You: They use Jira for tickets, Slack for chat, and Notion for docs.
     Main frustrations: context switching, missed updates due to time
     zones, unclear task ownership.

Claude: The workflow has completed the research phase.

        Current step: Documenting functional requirements
        Progress: 35%

        Based on your input, the PRD is focusing on:
        - Unified workspace reducing context switching
        - Smart notifications respecting time zones
        - Clear ownership with handoff protocols

        Would you like to add any specific features or constraints?

You: Yes, add integration with GitHub for automatic task updates
     when PRs are merged.

Claude: Added to requirements. The workflow continues...

        Progress: 60%
        Current step: Creating acceptance criteria

        [Workflow continues until completion]

You: Check status of FAOS workflow wfrun_task_mgmt_001

Claude: Workflow completed!

        PRD: Task Management for Remote Teams

        Deliverables:
        - Full PRD document (45 pages)
        - 4 user personas
        - 28 functional requirements (MoSCoW prioritized)
        - 15 non-functional requirements
        - 42 acceptance criteria
        - Success metrics dashboard spec

        [Shows PRD summary and offers to display sections]

Tips for Better PRDs​

Do​

  • Provide context upfront - Competitors, constraints, target users
  • Be specific - "Small businesses with 1-50 employees" not just "businesses"
  • Include constraints - Budget, timeline, technical limitations
  • Ask for iterations - "Make the acceptance criteria more specific"

Don't​

  • Rush the process - Let workflows complete their analysis
  • Skip research - Good PRDs start with market understanding
  • Ignore edge cases - Ask agents to consider failure scenarios
  • Forget metrics - Always define how success will be measured