nicole-pm

Translate product ideas into validated PRDs, epics, and user stories.

3|1|Updated May 12, 2026
One-click install
npx skills add https://github.com/LumenWipe/lumenwipe --skill nicole-pm-lumenwipe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nicole-pm
Source: https://github.com/LumenWipe/lumenwipe/tree/main/.claude/skills/nicole-pm
Command: npx skills add https://github.com/LumenWipe/lumenwipe --skill nicole-pm-lumenwipe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns ambiguous product ideas and stakeholder needs into validated requirements, focused PRDs, and development-ready planning artifacts.

Core Features & Use Cases

  • Requirements Discovery: Conduct user interviews and relentlessly clarify the underlying problem and desired outcomes.
  • Product Planning: Create, update, and validate PRDs, epics, and user stories that development teams can execute.
  • Alignment Reviews: Check that product requirements, UX, architecture, and implementation plans remain consistent.
  • Use Case: Use Nicole to refine a new product concept into a small validated increment, then produce the PRD and epics needed to guide development.

Quick Start

Ask Nicole to interview you about a product idea and create a concise, development-ready PRD.

Frequently Asked Questions about nicole-pm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn ambiguous product ideas into development-ready PRDs?

To turn ambiguous product ideas into development-ready PRDs, this Skill conducts user interviews to clarify the underlying problem and desired outcomes, then translates stakeholder needs into focused product requirements documents.

What is the best way to break down product requirements into epics and user stories?

The best way to break down product requirements into epics and user stories is through guided product planning workflows that validate PRDs and structure development-ready increments for your engineering teams.

How does requirements discovery work for new product concepts?

Requirements discovery works by conducting user interviews to relentlessly clarify the problem and desired outcomes, validating a new product concept before generating planning artifacts like PRDs and epics.

Can I use this to check alignment between product requirements and architecture plans?

Yes, you can use this to check alignment between product requirements and architecture plans through alignment reviews that ensure UX, architecture, and implementation remain consistent across initiatives.

Do I need project customization to create user stories from stakeholder needs?

Yes, you need project customization and persistent context to create user stories from stakeholder needs, as persona-driven product management workflows require planning configuration to guide the process.

When should I not use automated product planning for requirements discovery?

You should not use automated product planning when you lack clear stakeholder needs or desired outcomes, as translating ambiguous ideas into validated epics requires active interview-driven clarification.