Product Owner: PRD Creation

Generate a comprehensive Product Requirements Document following the Single Source of Truth principle.

Prerequisites

• Feature must exist with status created

Workflow Enforcement

Verify:

1. Feature exists at .hefesto/features/{feature_id}/feature.json
2. Feature status is created

If not met, show error with correct command.

Process

Phase 1: Feature Validation

1. Read .hefesto/features/{feature_id}/feature.json
2. Verify status is created
3. Load the original request and description

Phase 2: Overlap Analysis (Mandatory)

1. Read all existing PRDs: .hefesto/features/*/prd.md
2. Analyze for:
   • Duplicate requirements: Same functionality in different features
   • Scope conflicts: Overlapping areas of responsibility
   • Hidden dependencies: Undocumented links between features
   • Contradictions: Conflicting specifications

Phase 3: Project Investigation

Explore the codebase to understand:

• Existing patterns and conventions
• Technology stack and constraints
• Related functionality already implemented

Phase 4: PRD Generation

Write .hefesto/features/{feature_id}/prd.md:

# PRD: {Feature Title}

## Metadata
- **Feature ID**: {id}
- **Created**: {date}
- **Author**: {author}
- **Status**: Draft

## Gap Analysis

### Overlap with Existing Features
{findings from Phase 2}

### Dependencies
{identified dependencies}

## Executive Summary
{2-3 sentence summary}

## Problem Statement
{What problem does this solve?}

## Target Users
{Who will use this feature?}

## Scope

### In Scope
- {What this feature WILL do}

### Out of Scope
- {What this feature will NOT do}

## Functional Requirements

### FR-001: {Requirement Name}
- **Description**: {Detailed description}
- **Priority**: {P0/P1/P2/P3}
- **Acceptance Criteria**:
  - [ ] {Criterion 1}
  - [ ] {Criterion 2}

## Non-Functional Requirements
{Performance, security, accessibility}

## User Flows

### Flow 1: {Flow Name}
1. User does X
2. System responds with Y
3. User sees Z

## Technical Considerations
{Architecture notes, API design}

## Open Questions
{Unresolved questions}

## Notes
{Additional context}

Phase 5: Status Update

Update feature.json:

• status: prd_created
• phase: prd
• workflow.prd_created: true

Phase 6: Validation

Verify:

• PRD file exists
• All required sections present
• At least 1 functional requirement defined
• Acceptance criteria exist

Output

✅ PRD Created Successfully

Feature: {title}
Path: .hefesto/features/{id}/prd.md

Summary:
- Functional Requirements: 8
- Non-Functional Requirements: 3
- User Flows: 4
- Overlap Warnings: 2 (see Gap Analysis)

→ Next (PO): po:stories {id}