li-prd

Convert product ideas into structured PRDs with MVP scope and success criteria.

79|18|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jiangjiax/li-skills --skill li-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: li-prd
Source: https://github.com/jiangjiax/li-skills/tree/main/li-prd
Command: npx skills add https://github.com/jiangjiax/li-skills --skill li-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you convert a rough product idea into a structured, team-ready PRD with clear customer journey, boundaries, MVP scope, and measurable success criteria.

Core Features & Use Cases

  • Guided PRD creation (6-question intake): Collects essential inputs like Why Now, target user, status quo, success metrics, out-of-scope items, and MVP definition before drafting.
  • PRD template generation: Produces a complete PRD draft covering one-sentence description, problem/why/viral skepticism, goals and scope, customer journey, metrics, press-story, risks, and open questions.
  • Quality self-check & next-step recommendations: Includes a verification checklist for credibility and a set of follow-up skills for positioning, review, validation, and workflow coverage.

Quick Start

Ask it to: generate a PRD for your product idea so you can align your team on what to build next.

Frequently Asked Questions about li-prd

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

FAQPage Schema
How do I write a PRD for an MVP when I only have a rough product idea?

To write a PRD for an MVP from a rough idea, use a guided intake process to define your target user, success metrics, and scope. This structures limited information into a team-ready document with clear customer journey and MVP boundaries before development starts.

What sections should be included in a product requirements document for a hackathon project?

A PRD for a hackathon project should include a one-sentence description, problem statement, goals, scope, customer journey, success metrics, risks, and open questions. This ensures the team aligns on what to build next under time constraints.

Can I generate a PRD draft without fully clarified product requirements?

Yes, you can generate a PRD draft from partially clarified information by running a guided intake. It collects six essential inputs like why now, target user, and out-of-scope items to produce a structured document without needing complete specifications.

How do you define success metrics in a product requirements document?

Define success metrics in a PRD by establishing measurable criteria during the initial intake phase. This involves specifying what success looks like for the target user and the product, ensuring the MVP scope is aligned with actionable and trackable goals.

What is the best way to structure a customer journey in a PRD?

The best way to structure a customer journey in a PRD is to map it alongside the problem statement and MVP scope. This clarifies how the target user interacts with the product, ensuring the development team understands the intended user experience.