Skip to content
Moira Documentation

PRD Creation

PRD (Product Requirements Document) creation workflow with completeness guarantees through mandatory sections and data-backed decisions. Ensures problem-first approach with measurable outcomes.

Start

Section titled “Start”
Terminal window
mcp__moira__start({ workflowId: "prd-creation" })

Process

Section titled “Process”
flowchart LR
    A[Problem] --> B[Research]
    B --> C[Solution]
    C --> D[User Stories]
    D --> E[Edge Cases]
    E --> F[Metrics]
    F --> G[Assumptions]
    G --> H[Output]

Steps

Section titled “Steps”
StepActionOutput
1. ProblemDefine problem statement, target users, urgency, cost of inactionConcrete problem definition
2. ResearchGather data from analytics, interviews, support ticketsData-backed insights
3. SolutionDescribe solution, in/out of scope, constraintsSolution specification
4. User StoriesWrite stories with testable acceptance criteria (min 3 AC each)Testable requirements
5. Edge CasesDocument non-standard scenarios (min 5)Edge case coverage
6. MetricsDefine primary metric with target and measurement methodMeasurable success criteria
7. AssumptionsList assumptions with validation methodsExplicit assumptions
8. OutputFinal PRD documentComplete PRD

Features

Section titled “Features”

Problem-First Approach

Section titled “Problem-First Approach”
ElementRequirement
Problem statementSpecific and measurable
Target usersClearly defined segment
UrgencyTimeline and business impact
Cost of inactionWhat happens if not solved

Data-Backed Decisions

Section titled “Data-Backed Decisions”

Each statement requires a source:

  • Analytics data
  • User interviews
  • Support tickets
  • Competitor research

Testable Acceptance Criteria

Section titled “Testable Acceptance Criteria”
RequirementDescription
Minimum count3 AC per user story
VerifiabilityEach AC testable by autotest or manually
SpecificityNo abstract “works correctly”

Measurable Metrics

Section titled “Measurable Metrics”
  • Primary metric (north star) with specific target
  • Timeline for achievement
  • Measurement method defined and feasible

Explicit Assumptions

Section titled “Explicit Assumptions”
ElementDescription
AssumptionClear statement of what is assumed
Validation methodHow to verify the assumption
Impact if wrongConsequences of invalid assumption

Example Node Configuration

Section titled “Example Node Configuration”
{
  "id": "define-problem",
  "type": "agent-directive",
  "directive": "Define the problem statement with target users, urgency, and cost of inaction. Be specific and measurable.",
  "completionCondition": "Problem statement includes specific target users, measurable impact, and cost of inaction",
  "connections": {
    "next": "research-data"
  }
}
Section titled “Related”