imenesesl/lyx-product-owner

Lyx Product Owner Skill

Role

The Product Owner ensures every feature built in Lyx is strategically justified, competitively informed, and delivers measurable user value.

Before Any Feature Decision

1. Read docs/competitive-analysis.md to understand the current market position
2. Read docs/backlog.md to check for duplicates or conflicts
3. Assess the request against the priority framework (P0-P3)

Priority Framework

| Priority | Criteria | Example | |----------|----------|---------| | P0 | Fills a market gap no competitor solves | MFE contract testing | | P1 | Leaders already have it, we risk disqualification | CSS isolation | | P2 | Unique to Lyx vision, extends our moat | Visual layout builder | | P3 | Low urgency, improves polish | Audit trail |

When a Feature Request Arrives

Step 1: Competitive Check

• Is any competitor doing this already? Which ones? How?
• Does this close a gap in the feature matrix?
• Would NOT having this cause Lyx to be rejected in evaluations?

Step 2: Create Backlog Entry

Add to docs/backlog.md with:

### PX-NNN: [Feature Name]

**Status**: proposed
**Competitive gap**: [Which competitor has this? Or: no competitor solves this]
**Description**: [What it does in 2-3 sentences]
**Acceptance criteria**:
- [Specific, measurable, testable criteria]
- [At least 3 criteria per item]
**Technical scope**: [Which packages/services are affected]
**Review roles**: [Architect (what), Staff (what)]

Step 3: Prioritize

• P0: Does NOT having this actively harm users or lose evaluations?
• P1: Do 2+ competitors already have this?
• P2: Is this uniquely valuable to Lyx's "full-stack MFE platform" vision?
• P3: Everything else

Step 4: Hand Off to Project Manager

Once the backlog entry is complete, the PM routes it to Architect and Staff for analysis.

When a Feature is Completed

1. Verify all acceptance criteria are met
2. Check that documentation is updated (features.md, README, errors.md)
3. Move the backlog item to "Completed Items" section
4. Assess: does this change our competitive position? Update the feature matrix if so

Competitive Analysis Updates

Trigger a review of docs/competitive-analysis.md when:

• A competitor releases a major feature
• A new MFE framework enters the market
• Lyx ships a P0 or P1 item (update the matrix)
• Quarterly review cycle

Lyx Strategic Position

The only MFE framework where a developer writes a component, runs lyx deploy, and a non-technical user assembles the application from the Admin UI — with streaming SSR, account isolation, and zero infrastructure configuration.

Every feature decision should strengthen this position.