ls-research

Explore product direction and produce a Product Requirements Document (PRD).

3|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/liminal-ai/liminal-spec --skill ls-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-research
Source: https://github.com/liminal-ai/liminal-spec/tree/main/plugins/liminal-spec/skills/ls-research
Command: npx skills add https://github.com/liminal-ai/liminal-spec --skill ls-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms a raw vision or idea into a structured Product Requirements Document (PRD), clarifying product direction and scoping features before implementation begins.

Core Features & Use Cases

  • Vision to PRD: Converts high-level ideas into actionable product requirements.
  • Feature Scoping: Helps define clear boundaries for features, including what's in and out of scope.
  • Stakeholder Alignment: Facilitates agreement on product direction by producing a reviewable document.
  • Use Case: You have a new app idea but aren't sure which features to prioritize. This Skill helps you explore the problem space, define target users, and outline potential features, resulting in a PRD that guides the next steps.

Quick Start

Use the ls-research skill to explore product direction and produce a PRD for a new task management feature.

Frequently Asked Questions about ls-research

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

FAQPage Schema
How do I turn a product vision into a PRD?

To turn a product vision into a PRD, you need to frame the problem, define target users, draft feature candidates, set scope boundaries, and define success metrics to align stakeholders on the initiative.

What is the best way to define feature scope for a new app idea?

Defining feature scope involves exploring the problem space and setting clear boundaries for what features are in or out of scope, ensuring stakeholder alignment before moving into feature specification and Epic creation.

How do I gather product requirements and align stakeholders?

Gathering product requirements and aligning stakeholders involves framing problems and defining context to produce a reviewable Product Requirements Document that clarifies product direction and guides subsequent phases.

When do I need a Product Requirements Document for product strategy?

You need a Product Requirements Document when you have a high-level idea or new app feature but are unsure which features to prioritize, serving as an optional precursor to guide feature specification and implementation.

Can I use this to explore product direction before creating Epics?

Yes, you can explore product direction and scope features to produce a PRD that informs subsequent phases like Epic creation, ensuring stakeholder alignment on initiatives before detailed feature specification begins.

What is the difference between product research and writing a PRD?

Product research explores the problem space, target users, and feature candidates, while writing a PRD formalizes that research into a reviewable document with scope boundaries and success metrics to align stakeholders.