Afrexai Prd Engine

# PRD Engine — Product Requirements That Ship

Complete product requirements methodology: from idea to spec to shipped feature. Not just a JSON template — a full system for writing PRDs that developers actually follow and stakeholders actually approve.

## When to Use This Skill

- Turning a vague idea into a buildable specification
- Writing PRDs for new features, products, or major refactors
- Reviewing/improving existing PRDs before sprint planning
- Breaking epics into right-sized user stories
- Creating technical design documents alongside product specs
- Preparing specs for AI coding agents (Claude Code, Cursor, Copilot)

---

## Phase 1: Discovery Brief

Before writing a single requirement, answer these questions. Skip this and you'll rewrite the PRD 3 times.

### Problem Validation Checklist

```yaml
discovery_brief:
  problem:
    statement: "" # One sentence. If you need two, you don't understand it yet.
    who_has_it: "" # Specific persona, not "users"
    frequency: "" # Daily? Weekly? Once? (daily problems > occasional ones)
    current_workaround: "" # What do they do today? (no workaround = maybe not a real problem)
    evidence:
      - type: "" # support_ticket | user_interview | analytics | churned_user | sales_objection
        detail: ""
        date: ""

  impact:
    users_affected: "" # Number or percentage
    revenue_impact: "" # $ at risk or $ opportunity
    strategic_alignment: "" # Which company goal does this serve?

  constraints:
    deadline: "" # Hard date or flexible?
    budget: "" # Engineering weeks available
    dependencies: "" # What must exist first?
    regulatory: "" # Any compliance requirements?

  success_metrics:
    primary: "" # ONE metric that defines success
    secondary: [] # 2-3 supporting metrics
    measurement_method: "" # How will you actually measure this?
    target: "" # Specific number, not "improve"
    timeframe: "" # When do you expect to see results?
```

### Problem Statement Formula

**[Persona] n...

# PRD Engine — Product Requirements That Ship

The most comprehensive PRD skill on ClawHub. Not just a JSON template — a complete product requirements methodology from discovery to post-launch review.

## What You Get

- **Discovery Brief** — Problem validation checklist with kill criteria (stop bad PRDs before they start)
- **Full PRD Template** — 7-section document with edge cases, release plan, success metrics
- **Quality Rubric** — 100-point scoring system across 7 dimensions (score before sharing)
- **INVEST Story Methodology** — Right-sized stories with verifiable acceptance criteria
- **AI Agent Mode** — Optimized story format for Claude Code, Cursor, Copilot (file paths, verification commands, done-when)
- **Dependency Pyramid** — 6-level ordering system so you never build UI before the API exists
- **Splitting Strategies** — 6 patterns for breaking XL stories into shippable slices
- **Post-Launch Review** — Template for measuring if the feature actually worked
- **Progress Tracking** — Velocity + completion + blocker escalation

## Install

```bash
clawhub install afrexai-prd-engine
```

## Quick Start

```
"Write a PRD for [feature name]"
"Break this into stories: [feature description]"
"Review this PRD and score it"
"Make these stories agent-ready for Claude Code"
```

## Why This Over Alternatives

| Feature | Basic PRD Skills | PRD Engine |
|---------|-----------------|------------|
| Problem validation | ❌ | ✅ Discovery brief + kill criteria |
| Story methodology | Basic JSON | INVEST + sizing + 6 split strategies |
| Quality scoring | ❌ | ✅ 100-point rubric, 7 dimensions |
| AI agent support | ❌ | ✅ File paths, commands, done-when |
| Edge case coverage | ❌ | ✅ Empty, error, slow, permissions, concurrent |
| Post-launch review | ❌ | ✅ Metrics + retro + iterate/kill decision |
| Approval workflow | ❌ | ✅ Review checklist + common feedback fixes |

## ⚡ Level Up

Want a complete product management system with market analysis, competitive po...