From nickcrew-claude-ctx-plugin
Generates PRDs, prioritizes feature backlogs using RICE/MoSCoW, writes user stories with acceptance criteria, and defines product metrics/KPIs.
npx claudepluginhub nickcrew/claude-cortexThis skill uses the workspace's default tool permissions.
This skill enables structured product management work—from writing comprehensive PRDs and user stories through feature prioritization and metrics definition. It provides repeatable frameworks (RICE scoring, MoSCoW, OKR-aligned roadmaps) and document templates grounded in real product scenarios. The output is always decision-ready: actionable artifacts that engineering, design, and stakeholders ...
Generates Product Requirements Documents (PRDs) with user stories, success metrics, scope, technical considerations, and risks for product features.
Generates structured PRDs with problem, context, solution, user stories, acceptance criteria, metrics, risks, and out-of-scope items. Iteratively gathers info via questions, reviews docs/issues/templates.
Writes structured, evidence-based PRDs with measurable goals, prioritized requirements, success metrics, and scope boundaries. Use for PRD, product spec, or feature requirements requests.
Share bugs, ideas, or general feedback.
This skill enables structured product management work—from writing comprehensive PRDs and user stories through feature prioritization and metrics definition. It provides repeatable frameworks (RICE scoring, MoSCoW, OKR-aligned roadmaps) and document templates grounded in real product scenarios. The output is always decision-ready: actionable artifacts that engineering, design, and stakeholders can align on.
| Task | Framework/Template |
|---|---|
| Feature prioritization | RICE score: (Reach × Impact × Confidence) / Effort |
| Backlog triage | MoSCoW: Must have / Should have / Could have / Won't have |
| User story format | "As a [user], I want [action] so that [benefit]" |
| Acceptance criteria | Given/When/Then (BDD-style) |
| Success metrics | Primary: 1 north star. Secondary: 3–5 supporting. Guardrails: 2–3 don't-break metrics |
| PRD sections | Overview → Problem → Goals → Users → Requirements → Metrics → Risks → Timeline |
| Impact sizing | 1–5 scale: 1=minimal, 3=moderate, 5=massive uplift |
| Effort sizing | T-shirt: XS/S/M/L/XL; or story points; or person-weeks |
PRD Template:
Feature Name: [Name] Author: [PM Name] | Date: [Date] | Status: Draft / Review / Approved Engineering Owner: | Design Owner: | Launch Target:
1. Overview (TL;DR) One paragraph: what we're building, why, and the expected business impact.
2. Problem Statement
3. Goals and Non-Goals
| Goals | Non-Goals |
|---|---|
| ✅ Users can complete X without Y friction | ❌ This does not redesign the entire onboarding flow |
| ✅ Reduce support tickets about Z by 30% | ❌ This does not support mobile in V1 |
4. User Personas Who are the primary users? List 1–3 personas with their role, context, and motivation.
5. Functional Requirements List every user-facing behavior the feature must support, organized by user flow:
6. Non-Functional Requirements
7. Success Metrics
8. Risks and Mitigations
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [Risk] | High/Med/Low | High/Med/Low | [Plan] |
9. Open Questions
10. Launch Plan
RICE score = (Reach × Impact × Confidence) / Effort
Reach: How many users affected per quarter? (raw number) Impact: Effect per user: 3=massive, 2=high, 1=medium, 0.5=low, 0.25=minimal Confidence: How sure are we? 100%=high, 80%=medium, 50%=low Effort: Person-months required
Feature A: Reach=5000, Impact=2, Confidence=80%, Effort=2 months
RICE = (5000 × 2 × 0.8) / 2 = 4,000
Feature B: Reach=1000, Impact=3, Confidence=90%, Effort=0.5 months
RICE = (1000 × 3 × 0.9) / 0.5 = 5,400 ← prioritize this first
MoSCoW for sprint planning:
Format: As a [user type], I want [capability] so that [benefit].
Rules for good user stories:
Example:
As a free-plan user, I want to upgrade to Pro with one click from within the app so that I don't have to navigate to a separate billing page and lose my context.
For each user story, write 2–5 acceptance criteria in BDD format:
Scenario: Successful upgrade flow
Given I am logged in as a free-plan user
And I am on any page in the app
When I click "Upgrade to Pro" in the nav bar
Then I should see the upgrade modal with pricing details
And the modal should pre-fill my account email
Scenario: Failed payment
Given I am on the upgrade modal
When I submit payment with a declined card
Then I should see the error message "Payment declined. Please try another card."
And my account should remain on the free plan
And no charge should appear on my card
For every feature, define metrics in three tiers:
Tier 1 — Primary (North Star): The one metric that proves the feature is delivering value. Tier 2 — Secondary: Supporting metrics that explain why the primary metric moved. Tier 3 — Guardrails: Metrics that must NOT regress (existing feature health).
Example for an upgrade flow feature:
Input: "We want to add in-app notifications so users don't miss important events."
PRD excerpt:
Feature Name: In-App Notification Center Status: Draft | Launch Target: Q2 2024 | Effort: M (3 engineers, 6 weeks)
Problem Statement: Users miss critical events (payment failures, team invitations, limit warnings) because they only receive emails, which have a 22% open rate. This results in 340 monthly support tickets from users who say they "didn't know" about an issue. Churn analysis shows 18% of churned users had an unresolved payment failure 7+ days before cancellation.
Goals: Enable users to see and act on critical account events without leaving the app. Target: reduce missed-event support tickets by 50% in 90 days.
Non-Goals: Push notifications (mobile), email digest redesign, third-party integrations.
Requirements:
Primary metric: Support tickets tagged "missed-event" (target: −50% in 90 days) Secondary: Notification open rate, CTA click rate per notification type Guardrails: Page load time on nav (must stay < 200ms), email open rate (must not drop)
Input: 5 features competing for next quarter's roadmap.
| Feature | Reach | Impact | Confidence | Effort (months) | RICE Score |
|---|---|---|---|---|---|
| SSO / SAML login | 800 enterprise users | 3 (massive — blocks enterprise sales) | 90% | 2 | 1,080 |
| Dark mode | 12,000 all users | 0.5 (minimal productivity gain) | 80% | 1 | 4,800 |
| Bulk CSV export | 2,500 power users | 2 (high — replaces manual workaround) | 90% | 0.5 | 9,000 ← #1 |
| AI summary feature | 5,000 users | 2 (high) | 50% | 3 | 1,667 |
| Mobile app | 12,000 all users | 2 (high) | 70% | 8 | 2,100 |
Recommendation: