Product Owner: Feature Management

Router command for feature lifecycle management.

Routing

Parse the first argument to determine the action:

First Arg	Action	Description
(none)	List	Show all features with status
create	Create	Create a new feature
accept	Accept	Sign off on completed feature

---

Strategy: List Features

Trigger: No arguments provided

Behavior

1. Scan for features: Search .hefesto/features/*/feature.json

2. Display each feature with:

   • ID and title
   • Current status and phase
   • Progress bar with percentage
   • Story checklist (completed/total)
   • Owner indicators (PO/Dev work pending)
   • Next recommended action

3. Determine next action for each feature:

   • No PRD → po:prd <id>
   • No stories → po:stories <id>
   • Stories need planning → dev:plan story <path>
   • Stories need coding → dev:code story <path>
   • Stories need testing → dev:test story <path>
   • Stories need tech docs → dev:document story <path>
   • Stories need validation → po:validate story <path>
   • Stories need user docs → po:document story <path>
   • All stories done → dev:test feature <id>
   • Feature tested → po:validate feature <id>
   • Feature validated → po:document feature <id>
   • Feature documented → po:feature accept <id>

Output Format

📋 HEFESTO - Feature Dashboard
═══════════════════════════════════════

Feature: User Authentication System
ID: 2025-01-15-143052-user-auth
Status: in_progress | Phase: coding
Progress: ████████░░░░░░░░ 50% (3/6 stories)

Stories:
  ✅ 001-login-form [complete]
  ✅ 002-password-validation [complete]
  🔧 003-session-management [dev:test] ← DEV
  ⏳ 004-logout-flow [dev:plan]
  ⏳ 005-password-reset [defined]

→ Next (DEV): dev:test story .hefesto/features/.../003-session-management

───────────────────────────────────────
Summary: 3 features | 1 active | 2 completed

---

Strategy: Create Feature

Trigger: First argument is create

Syntax

po:feature create <description>

Behavior

1. Check for overlap:

   • Read all existing feature.json files
   • Analyze if the new feature overlaps with existing ones
   • If significant overlap found, warn and ask for confirmation

2. Generate feature ID:

   • Format: {YYYY-MM-DD-HHmmss}-{slug}
   • Slug: Keywords from description, lowercase, no accents, max 30 chars
   • Example: 2025-01-15-143052-user-auth

3. Create directory structure:

   .hefesto/features/{id}/
   └── feature.json
   

4. Write feature.json:

   {
     "version": "1.0.0",
     "id": "{generated_id}",
     "title": "{extracted_title}",
     "description": "{full_description}",
     "original_request": "{exact_user_input}",
     "created_at": "{ISO_timestamp}",
     "updated_at": "{ISO_timestamp}",
     "status": "created",
     "phase": "initial",
     "progress": 0,
     "stories": [],
     "workflow": {
       "prd_created": false,
       "stories_created": false,
       "stories_complete": false,
       "feature_tested": false,
       "feature_validated": false,
       "feature_documented": false,
       "accepted": false
     }
   }
   

5. Recommend next step: po:prd {id}

Output Format

✨ Feature Created Successfully

ID: 2025-01-15-143052-user-auth
Title: User Authentication System
Path: .hefesto/features/2025-01-15-143052-user-auth/

→ Next (PO): po:prd 2025-01-15-143052-user-auth

---

Strategy: Accept Feature

Trigger: First argument is accept

Syntax

po:feature accept <feature_id>

Prerequisites

Feature workflow must have:

• feature_tested: true
• feature_validated: true
• feature_documented: true

Behavior

1. Verify prerequisites: All workflow steps complete
2. Create completion summary: .hefesto/features/{id}/completion-summary.md
3. Update feature.json:

   {
     "status": "accepted",
     "phase": "complete",
     "accepted_at": "{timestamp}",
     "progress": 100,
     "workflow": {
       "accepted": true
     }
   }
   

Output Format

🎉 Feature Accepted!

══════════════════════════════════════════════════════════
  User Authentication System
══════════════════════════════════════════════════════════

Summary:
  ✅ 5 stories completed
  ✅ All tests passing
  ✅ All validations passed
  ✅ Documentation complete

Timeline:
  Created:  2025-01-15
  Accepted: 2025-01-20
  Duration: 5 days

Deliverables:
  📄 PRD: .hefesto/features/{id}/prd.md
  📖 User Guide: .hefesto/features/{id}/docs/user-guide.md
  🔧 Technical Docs: .hefesto/features/{id}/docs/technical.md

Recommended Next Steps:
  1. Merge feature branch to main
  2. Deploy to staging
  3. Update project CHANGELOG.md

Great work! The feature is ready for release. 🚀

Cannot Accept

If prerequisites not met:

❌ Cannot Accept Feature

Feature: User Authentication
ID: 2025-01-15-143052-user-auth

The following steps are incomplete:

  ❌ feature_documented: false
     → Run: po:document feature 2025-01-15-143052-user-auth

Complete the missing steps before accepting.

---

Feature Statuses

Status	Description
created	Feature initialized, needs PRD
prd_created	PRD written, needs stories
stories_created	Stories generated, work can begin
in_progress	Stories being worked on
stories_complete	All stories finished
feature_tested	Integration tests passed
feature_validated	Feature meets requirements
feature_documented	Documentation complete
accepted	PO signed off, feature complete