Product Owner: User Stories Generation

Generate independent, atomic user stories from the PRD following the Independence Principle.

Prerequisites

• Feature must have status prd_created

Workflow Enforcement

Verify:

1. Feature exists at .hefesto/features/{feature_id}/
2. PRD exists at .hefesto/features/{feature_id}/prd.md
3. Feature status is prd_created

Independence Principle

Each story must satisfy:

1. Independence: Can be implemented without other incomplete stories
2. Atomicity: Single, complete piece of functionality
3. Testability: Clear, verifiable acceptance criteria
4. Reasonable scope: One focused coding session
5. Logical ordering: Respects dependencies

Process

Phase 1: Locate Feature

1. Verify feature exists
2. Load feature.json
3. Confirm status is prd_created

Phase 2: Conflict Analysis

1. Scan all features for existing stories
2. Identify potential conflicts:
   • Stories modifying same files
   • Circular dependencies
   • Duplicate functionality

Phase 3: Read and Interpret PRD

1. Read .hefesto/features/{feature_id}/prd.md
2. Extract functional requirements
3. Map requirements to stories
4. Identify dependencies

Phase 4: Create Directory Structure

.hefesto/features/{feature_id}/
├── feature.json
├── prd.md
└── stories/
    ├── 001-{story-slug}/
    │   └── user-story.md
    ├── 002-{story-slug}/
    │   └── user-story.md
    └── ...

Phase 5: Generate Stories

For each story, create user-story.md:

# User Story: {Title}

## Metadata
- **Story ID**: {nnn}-{slug}
- **Feature**: {feature_id}
- **Priority**: {1-4}
- **Status**: defined
- **Created**: {timestamp}
- **Requirements**: FR-001, FR-002

## Conflict Analysis

### Files Likely Modified
- `src/components/...`
- `src/api/...`

### Potential Conflicts
{Analysis of overlapping changes}

## Dependencies

### Required Before This Story
- None (or list story IDs)

### Enables These Stories
- 002-password-validation

## User Story

**As a** {user type}
**I want to** {action/capability}
**So that** {benefit/value}

## Acceptance Criteria

1. [ ] Given {context}, when {action}, then {result}
2. [ ] Given {context}, when {action}, then {result}

## Scenarios

### Scenario 1: {Happy Path}
**Given** {initial state}
**When** {action taken}
**Then** {expected outcome}

### Scenario 2: {Error Case}
**Given** {initial state}
**When** {invalid action}
**Then** {error handling}

## Technical Notes
{Implementation hints}

## Out of Scope
{What this story does NOT include}

Phase 6: Prioritization

• Priority 1: Foundational - enables other stories
• Priority 2: High value - core user features
• Priority 3: Complementary - enhances core
• Priority 4: Optional - nice to have

Phase 7: Update Feature Registry

Update feature.json:

• status: stories_created
• phase: stories
• workflow.stories_created: true
• stories: array of story metadata

Phase 8: Validation

Verify:

• Each story has valid user-story.md
• Stories numbered sequentially
• No circular dependencies
• All PRD requirements covered

Output

✅ User Stories Generated

Feature: {title}
Path: .hefesto/features/{id}/stories/

Stories Created:
  [P1] 001-login-form
  [P1] 002-password-validation
  [P2] 003-session-management
  [P2] 004-logout-flow
  [P3] 005-password-reset

Dependency Graph:
  001 → 002 → 003
            ↘ 004
  005 (independent)

→ Next (DEV): dev:plan story .hefesto/features/{id}/stories/001-login-form