Product Owner: User-Facing Documentation

Router command that creates user-facing documentation for stories or features.

Scope: User guides, how-to docs, release notes - documentation for end users.

Routing

Input	Strategy
story <path>	Story User Documentation
feature <id>	Feature User Documentation
<path> (auto-detect)	Detect from path pattern

---

Strategy: Story User Documentation

Trigger: po:document story <path> or auto-detected story path

Prerequisites

• Story status must be po_validated

Process

1. Gather Context:

   • Read user story for user perspective
   • Read dev documentation for implementation details
   • Understand the user flow

2. Create User Documentation: {story_path}/user-docs.md

# {Story Title} - User Guide

## Overview

{What this feature does for the user, in plain language}

## How to Use

### Getting Started

{Prerequisites the user needs}

### Step-by-Step

1. {Step 1 with screenshot reference if UI}
2. {Step 2}
3. {Step 3}

### Example

{Concrete example of using the feature}

## Tips

- {Helpful tip 1}
- {Helpful tip 2}

## Troubleshooting

### {Common Issue 1}

**Problem**: {What the user sees}
**Solution**: {How to fix it}

### {Common Issue 2}

**Problem**: {What the user sees}
**Solution**: {How to fix it}

## Related

- {Link to related features}

3. Update Status:
   • Story status → complete
   • Mark story as fully done in feature.json

Output

✅ Story User Documentation Complete

Story: {title}
Path: {story_path}/user-docs.md

Story is now COMPLETE.

Feature Progress: 3/5 stories complete

→ Next: Continue with remaining stories or proceed to feature-level work

---

Strategy: Feature User Documentation

Trigger: po:document feature <id> or auto-detected feature path

Prerequisites

• Feature must be feature_validated
• All stories must be complete

Process

1. Gather All Context:

   • Read PRD for feature overview
   • Read all story user docs
   • Understand complete user journey

2. Create Feature User Guide: .hefesto/features/{id}/docs/user-guide.md

# {Feature Title} - User Guide

## Introduction

{What this feature is and why it matters to users}

## Getting Started

### Prerequisites

- {Requirement 1}
- {Requirement 2}

### Quick Start

{5-step or less quick start}

## Features

### {Capability 1}

{Description and how to use}

### {Capability 2}

{Description and how to use}

## How-To Guides

### How to {Task 1}

1. {Step 1}
2. {Step 2}
3. {Step 3}

### How to {Task 2}

1. {Step 1}
2. {Step 2}

## Reference

### Settings

| Setting | Description | Default |
|---------|-------------|---------|
| {setting} | {description} | {default} |

### Keyboard Shortcuts

| Shortcut | Action |
|----------|--------|
| {key} | {action} |

## FAQ

### {Question 1}

{Answer}

### {Question 2}

{Answer}

## Troubleshooting

### {Issue 1}

**Symptom**: {What user sees}
**Cause**: {Why it happens}
**Solution**: {How to fix}

## Getting Help

{How to get support}

3. Create Release Notes: .hefesto/features/{id}/docs/release-notes.md

# Release Notes: {Feature Title}

## Version {version} - {date}

### New Features

- **{Feature 1}**: {Description}
- **{Feature 2}**: {Description}

### Improvements

- {Improvement 1}
- {Improvement 2}

### Known Issues

- {Issue 1}

### Upgrade Notes

{Any special instructions for upgrading}

4. Update Status:
   • workflow.feature_documented → true

Output

✅ Feature User Documentation Complete

Feature: {title}
ID: {id}

Documentation Created:
  📖 User Guide: .hefesto/features/{id}/docs/user-guide.md
  📋 Release Notes: .hefesto/features/{id}/docs/release-notes.md

Feature is ready for acceptance.

→ Next (PO): po:feature accept {id}

---

Documentation Principles

1. Write for users, not developers: No jargon, no implementation details
2. Task-oriented: Focus on what users want to accomplish
3. Progressive disclosure: Simple first, details available if needed
4. Examples everywhere: Show, don't just tell
5. Troubleshooting ready: Anticipate common problems