Skip to content

mattgierhart/PRD-driven-context-engineering / .claude/skills/prd-v03-features-value-planning

prd-v03-features-value-planning

Verified

Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Triggers on requests to define features, prioritize capabilities, scope MVP, map features to pricing tiers, identify parity vs. delta features, or when user asks "what features do we build?", "what's in MVP?", "which features matter?", "feature priority", "parity features", "what's our delta?". Consumes KPI- (Outcome Definition), BR- (Pricing Model, Moat), and CFD- (Market Moat Analysis) from v0.3. Outputs FEA- entries with strategic traceability and BR-FEA- governance rules. Feeds v0.4 User Journeys.

FileKindSize
SKILL.mdskill md8.4 KB
assets/competitive-feature-matrix.mdmarkdown3.6 KB
assets/fea.mdmarkdown2.2 KB
references/examples.mdmarkdown5.6 KB

assets/competitive-feature-matrix.md

View on GitHub
# Competitive Feature Matrix

Use this matrix to map features against competitors and identify parity/delta opportunities.

---

## Matrix Template

| Feature | Our Status | Competitor A | Competitor B | Competitor C | Type | Priority |
|---------|------------|--------------|--------------|--------------|------|----------|
| [Feature 1] | | | | | | |
| [Feature 2] | | | | | | |
| [Feature 3] | | | | | | |

### Status Legend

| Symbol | Meaning |
|--------|---------|
| โœ… | Shipped / Available |
| ๐Ÿšง | Building / In progress |
| ๐Ÿ“‹ | Planned |
| โŒ | Not available |
| โž• | Our delta (we have, they don't) |
| โญ | Their strength (they're better) |

---

## Example: Scheduling Tool Matrix

| Feature | Us | Calendly | Acuity | SavvyCal | Type | Priority |
|---------|-----|----------|--------|----------|------|----------|
| Calendar sync | ๐Ÿšง | โœ… | โœ… | โœ… | Parity | P0 |
| Custom booking page | ๐Ÿšง | โœ… | โœ… | โœ… | Parity | P0 |
| Unlimited event types | โž• | โŒ (paid) | โŒ (paid) | โœ… | Delta | P0 |
| Team scheduling | ๐Ÿ“‹ | โœ… | โญ | โœ… | Parity | P1 |
| Round-robin | โŒ | โญ | โœ… | โœ… | Defer | P3 |
| Workflows/automation | โŒ | โญ | โŒ | โœ… | Defer | P3 |
| Offline mode | โž• | โŒ | โŒ | โŒ | Delta | P1 |

### Analysis from Example

**Parity requirements (P0)**:
- Calendar sync, custom booking page = table stakes
- Must match before users will consider switching

**Our deltas (competitive advantage)**:
- Unlimited event types โ†’ Price-based moat (they charge, we don't)
- Offline mode โ†’ Capability moat (they can't easily add)

**Defer (not MVP)**:
- Round-robin, workflows โ†’ Enterprise features, add post-PMF

---

## How to Complete This Matrix

### Step 1: List Competitor Features
Pull from CFD- entries (Competitive Landscape skill output):
- Feature lists from competitor websites
- G2/Capterra comparison pages
- User reviews mentioning features

### Step 2: Audit Usage (Critical)
Not all features matter. For each competitor feature, ask:
- Do users actually use this? (Check reviews, forums)
- Is it mentioned in buying decisions? (Check comparison threads)
- Is it a "checkbox feature" vs. core workflow?

**80/20 rule**: 20% of features drive 80% of value. Identify the 20%.

### Step 3: Classify Our Position
For each feature row:
- **Parity**: We must match to be considered
- **Delta**: We're better or unique
- **Defer**: Not essential for target segment

### Step 4: Assign Priority
Use this decision tree:

```
Is this feature used in core workflow?
โ”œโ”€ YES โ†’ Is competitor clearly better?
โ”‚   โ”œโ”€ YES โ†’ Parity (P0 if blocking, P1 if not)
โ”‚   โ””โ”€ NO โ†’ Can we be meaningfully better?
โ”‚       โ”œโ”€ YES โ†’ Delta (P0 if moat-building)
โ”‚       โ””โ”€ NO โ†’ Table stakes (P1)
โ””โ”€ NO โ†’ Defer (P2/P3 or cut)
```

---

## Matrix โ†’ FEA- Conversion

Each row becomes a FEA- entry:

| Matrix Column | FEA- Field |
|---------------|------------|
| Feature | FEA-XXX: [Name] |
| Our Status | Current state |
| Type | Type classification |
| Priority | Priority tier |
| Competitor columns | Competitor Comparison field |

**Evidence source**: The matrix itself becomes CFD- evidence for feature decisions.

---

## Anti-Patterns

| Problem | Signal | Fix |
|---------|--------|-----|
| Parity inflation | >70% marked "Parity, P0" | Audit actual usage; apply 80/20 |
| No deltas | Everything is parity or defer | Find undercut opportunity or reconsider market |
| Competitor-driven scope | Building features because "they have it" | Validate with user evidence (CFD-) |
| Ignoring strengths (โญ) | No plan for competitor advantages | Either match or position around |
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page โ€” title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "ไผš่ฎฎ็บช่ฆ".Stars: 108kUpdated Claude CodeCodexVerifiedInstall